<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 19:55:43 +0000</lastBuildDate>
    <item>
      <title>bdu:2021-02773</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2021-02773</link>
      <description>bdu:2021-02773</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2021-02773</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2021-25216 — CVE-2021-25216 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2021-25216</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2021-25216</guid>
    </item>
    <item>
      <title>certfr-2021-avi-325 — De multiples vulnérabilités ont été découvertes dans BIND. Elles
permettent à un attaquant de provoquer une exécution d…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2021-avi-325</link>
      <description>certfr-2021-avi-325</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2021-avi-325</guid>
    </item>
    <item>
      <title>EUVD-2026-174092</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-174092</link>
      <description>EUVD-2026-174092</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-174092</guid>
    </item>
    <item>
      <title>fkie_cve-2021-25216</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-25216</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2021-25216</guid>
    </item>
    <item>
      <title>GHSA-4vh7-r4m9-4w3v</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4vh7-r4m9-4w3v</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-4vh7-r4m9-4w3v</guid>
    </item>
    <item>
      <title>gsd-2021-25216</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-25216</link>
      <description>gsd-2021-25216</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-25216</guid>
    </item>
    <item>
      <title>ICSA-22-069-09 — Siemens SINEC INS</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-22-069-09</link>
      <description>&lt;p&gt;SQLite 3.30.1 mishandles pExpr-&amp;gt;y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c. Select in select.c in SQLite 3.30.1 allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage. lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service or possibly have unspecified other impact. SQLite 3.30.1 mishandles certain SELECT statements with a nonexistent VIEW, leading to an application crash. alter.c in SQLite through 3.30.1 allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements. pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns. exprListAppendList in window.c in SQLite 3.30.1 allows attackers to trigger an invalid pointer dereference because constant integer values in ORDER BY clauses of window definitions are mishandled. flattenSubquery in select.c in SQLite 3.30.1 mishandles certain uses of SELECT DISTINCT involving a LEFT JOIN in which the right-hand side is a view. This can cause a NULL pointer dereference (or incorrect results). SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This is caused by incorrect sqlite3WindowRewrite() error handling. zipfileUpdate in ext/misc/zipfile.c in SQLite…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SQLite 3.30.1 mishandles pExpr-&amp;gt;y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c. Select in select.c in SQLite 3.30.1 allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage. lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service or possibly have unspecified other impact. SQLite 3.30.1 mishandles certain SELECT statements with a nonexistent VIEW, leading to an application crash. alter.c in SQLite through 3.30.1 allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements. pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns. exprListAppendList in window.c in SQLite 3.30.1 allows attackers to trigger an invalid pointer dereference because constant integer values in ORDER BY clauses of window definitions are mishandled. flattenSubquery in select.c in SQLite 3.30.1 mishandles certain uses of SELECT DISTINCT involving a LEFT JOIN in which the right-hand side is a view. This can cause a NULL pointer dereference (or incorrect results). SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This is caused by incorrect sqlite3WindowRewrite() error handling. zipfileUpdate in ext/misc/zipfile.c in SQLite…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-22-069-09</guid>
    </item>
    <item>
      <title>msrc_CVE-2021-25216 — A second vulnerability in BIND's GSSAPI security policy negotiation can be targeted by a buffer overflow attack</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2021-25216</link>
      <description>msrc_CVE-2021-25216</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2021-25216</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:10650-1 — bind-9.16.20-1.4 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:10650-1</link>
      <description>&lt;p&gt;bind-9.16.20-1.4 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;bind-9.16.20-1.4 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:10650-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2021:1469-1 — Security update for bind</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2021:1469-1</link>
      <description>&lt;p&gt;Security update for bind&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for bind&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2021:1469-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-25216</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-25216</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: bind9, Ubuntu:16.04:LTS: bind9, Ubuntu:18.04:LTS: bind9, Ubuntu:20.04:LTS: 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; Ubuntu:Pro:14.04:LTS: bind9, Ubuntu:16.04:LTS: bind9, Ubuntu:18.04:LTS: bind9, Ubuntu:20.04:LTS: 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://cve.radiocsirt.org/vuln/ubuntu-cve-2021-25216</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2027 — Internet Systems Consortium BIND: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2027</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2027</guid>
    </item>
  </channel>
</rss>
