<?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>Wed, 07 Oct 2026 06:43:12 +0000</lastBuildDate>
    <item>
      <title>cnvd-2021-25672</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-25672</link>
      <description>cnvd-2021-25672</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-25672</guid>
    </item>
    <item>
      <title>EUVD-2026-40301</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-40301</link>
      <description>EUVD-2026-40301</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-40301</guid>
    </item>
    <item>
      <title>fkie_cve-2020-10995</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-10995</link>
      <description>&lt;p&gt;PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack uses a crafted reply by an authoritative name server to amplify the resulting traffic between the recursive and other authoritative name servers. Both types of service can suffer degraded performance as an effect. This is triggered by random subdomains in the NSDNAME in NS records. PowerDNS Recursor 4.1.16, 4.2.2 and 4.3.1 contain a mitigation to limit the impact of this DNS protocol issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack uses a crafted reply by an authoritative name server to amplify the resulting traffic between the recursive and other authoritative name servers. Both types of service can suffer degraded performance as an effect. This is triggered by random subdomains in the NSDNAME in NS records. PowerDNS Recursor 4.1.16, 4.2.2 and 4.3.1 contain a mitigation to limit the impact of this DNS protocol issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-10995</guid>
    </item>
    <item>
      <title>GHSA-g5gv-j2x8-cxr2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g5gv-j2x8-cxr2</link>
      <description>&lt;p&gt;PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack uses a crafted reply by an authoritative name server to amplify the resulting traffic between the recursive and other authoritative name servers. Both types of service can suffer degraded performance as an effect. This is triggered by random subdomains in the NSDNAME in NS records. PowerDNS Recursor 4.1.16, 4.2.2 and 4.3.1 contain a mitigation to limit the impact of this DNS protocol issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack uses a crafted reply by an authoritative name server to amplify the resulting traffic between the recursive and other authoritative name servers. Both types of service can suffer degraded performance as an effect. This is triggered by random subdomains in the NSDNAME in NS records. PowerDNS Recursor 4.1.16, 4.2.2 and 4.3.1 contain a mitigation to limit the impact of this DNS protocol issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g5gv-j2x8-cxr2</guid>
    </item>
    <item>
      <title>gsd-2020-10995</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-10995</link>
      <description>gsd-2020-10995</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-10995</guid>
    </item>
    <item>
      <title>openSUSE-SU-2020:0698-1 — Security update for pdns-recursor</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2020:0698-1</link>
      <description>&lt;p&gt;Security update for pdns-recursor&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for pdns-recursor&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2020:0698-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2020-10995</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-10995</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: pdns-recursor, Ubuntu:Pro:18.04:LTS: pdns-recursor, Ubuntu:Pro:20.04:LTS: pdns-recursor&lt;/p&gt;
&lt;p&gt;PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack uses a crafted reply by an authoritative name server to amplify the resulting traffic between the recursive and other authoritative name servers. Both types of service can suffer degraded performance as an effect. This is triggered by random subdomains in the NSDNAME in NS records. PowerDNS Recursor 4.1.16, 4.2.2 and 4.3.1 contain a mitigation to limit the impact of this DNS protocol issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: pdns-recursor, Ubuntu:Pro:18.04:LTS: pdns-recursor, Ubuntu:Pro:20.04:LTS: pdns-recursor&lt;/p&gt;
&lt;p&gt;PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack uses a crafted reply by an authoritative name server to amplify the resulting traffic between the recursive and other authoritative name servers. Both types of service can suffer degraded performance as an effect. This is triggered by random subdomains in the NSDNAME in NS records. PowerDNS Recursor 4.1.16, 4.2.2 and 4.3.1 contain a mitigation to limit the impact of this DNS protocol issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-10995</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0978 — Mehrere DNS Server: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0978</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in mehreren DNS Server Produkten ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in mehreren DNS Server Produkten 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-2024-0978</guid>
    </item>
  </channel>
</rss>
