<?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>Sun, 04 Oct 2026 05:06:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-25216 — A second vulnerability in BIND's GSSAPI security policy negotiation can be targeted by a buffer overflow attack</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2021-25216</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ISC BIND9&lt;/p&gt;
&lt;p&gt;In BIND 9.5.0 -&amp;gt; 9.11.29, 9.12.0 -&amp;gt; 9.16.13, and versions BIND 9.11.3-S1 -&amp;gt; 9.11.29-S1 and 9.16.8-S1 -&amp;gt; 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -&amp;gt; 9.17.1 of the BIND 9.17 development branch, BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND&amp;#39;s default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting values for the tkey-gssapi-keytab or tkey-gssapi-credential configuration options. Although the default configuration is not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in mixed-server environments that combine BIND servers with Active Directory domain controllers. For servers that meet these conditions, the ISC SPNEGO implementation is vulnerable to various attacks, depending on the CPU architecture for which BIND was built: For named binaries compiled for 64-bit platforms, this flaw can be used to trigger a buffer over-read, leading to a server crash. For named binaries compiled for 32-bit platforms, this flaw can be used to trigger a server crash due to a buffer overflow and possibly also to achieve remote code execution. We have determined that standard SPNEGO implementations are available in the MIT and Heimdal Kerberos libraries, which support a broad range of operating systems, rendering the ISC implementation unnecessar…&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 BIND 9.5.0 -&amp;gt; 9.11.29, 9.12.0 -&amp;gt; 9.16.13, and versions BIND 9.11.3-S1 -&amp;gt; 9.11.29-S1 and 9.16.8-S1 -&amp;gt; 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -&amp;gt; 9.17.1 of the BIND 9.17 development branch, BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND&amp;#39;s default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting values for the tkey-gssapi-keytab or tkey-gssapi-credential configuration options. Although the default configuration is not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in mixed-server environments that combine BIND servers with Active Directory domain controllers. For servers that meet these conditions, the ISC SPNEGO implementation is vulnerable to various attacks, depending on the CPU architecture for which BIND was built: For named binaries compiled for 64-bit platforms, this flaw can be used to trigger a buffer over-read, leading to a server crash. For named binaries compiled for 32-bit platforms, this flaw can be used to trigger a server crash due to a buffer overflow and possibly also to achieve remote code execution. We have determined that standard SPNEGO implementations are available in the MIT and Heimdal Kerberos libraries, which support a broad range of operating systems, rendering the ISC implementation unnecessar…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2021-25216</guid>
    </item>
  </channel>
</rss>
