<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 06:29:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-8619 — A buffer boundary check assertion in rdataset.c can fail incorrectly during zone transfer</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2020-8619</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ISC BIND9&lt;/p&gt;
&lt;p&gt;In ISC BIND9 versions BIND 9.11.14 -&amp;gt; 9.11.19, BIND 9.14.9 -&amp;gt; 9.14.12, BIND 9.16.0 -&amp;gt; 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -&amp;gt; 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains an empty non-terminal entry containing an asterisk (&amp;#34;*&amp;#34;) character, this defect cannot be encountered. A would-be attacker who is allowed to change zone content could theoretically introduce such a record in order to exploit this condition to cause denial of service, though we consider the use of this vector unlikely because any such attack would require a significant privilege level and be easily traceable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ISC BIND9&lt;/p&gt;
&lt;p&gt;In ISC BIND9 versions BIND 9.11.14 -&amp;gt; 9.11.19, BIND 9.14.9 -&amp;gt; 9.14.12, BIND 9.16.0 -&amp;gt; 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -&amp;gt; 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains an empty non-terminal entry containing an asterisk (&amp;#34;*&amp;#34;) character, this defect cannot be encountered. A would-be attacker who is allowed to change zone content could theoretically introduce such a record in order to exploit this condition to cause denial of service, though we consider the use of this vector unlikely because any such attack would require a significant privilege level and be easily traceable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2020-8619</guid>
    </item>
  </channel>
</rss>
