CVE-2020-10995
published 2020-05-19CVE-2020-10995: 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…
PriorityP340high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
4.37%
90.2th percentile
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.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | pdns-recursor | < pdns-recursor 4.3.1-1 (bookworm) | pdns-recursor 4.3.1-1 (bookworm) |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| opensuse | backports_sle | — | — |
| opensuse | leap | — | — |
| powerdns | recursor | 4.1.0 – 4.3.0 | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv7.5HIGH
vendor_debian7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2020-10995: pdns-recursor - PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently def...
vendor_debian·2020·CVSS 7.5
CVE-2020-10995 [HIGH] CVE-2020-10995: pdns-recursor - PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently def...
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.
Scope: local
bookworm: resolved (fixed in 4.3.1-1)
bullseye: resolved (fixed in 4.3.1-1)
forky: resolved (fixed in 4.3.1-1)
sid
GHSA
GHSA-g5gv-j2x8-cxr2: PowerDNS Recursor from 4
ghsa_unreviewed·2022-05-24
CVE-2020-10995 [MEDIUM] CWE-400 GHSA-g5gv-j2x8-cxr2: PowerDNS Recursor from 4
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.
OSV
CVE-2020-10995: PowerDNS Recursor from 4
osv·2020-05-19·CVSS 7.5
CVE-2020-10995 [HIGH] CVE-2020-10995: PowerDNS Recursor from 4
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers [epel-all]
bugzilla·2020-05-26·CVSS 7.5
CVE-2020-10995 [HIGH] CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers [epel-all]
CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changel
Bugzilla
CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers
bugzilla·2020-05-26·CVSS 7.5
CVE-2020-10995 [HIGH] CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers
CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers
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 impac
Bugzilla
CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers [fedora-all]
bugzilla·2020-05-26·CVSS 7.5
CVE-2020-10995 [HIGH] CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers [fedora-all]
CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM cha
http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00052.htmlhttp://www.nxnsattack.comhttps://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2020-01.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NMP72NJGKBWR5WEBXAWX5KSLQUDFTG6S/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PS4ZN5XGENYNFKX7QIIOUCQQHXE37GJF/https://www.debian.org/security/2020/dsa-4691http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00052.htmlhttp://www.nxnsattack.comhttps://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2020-01.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NMP72NJGKBWR5WEBXAWX5KSLQUDFTG6S/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PS4ZN5XGENYNFKX7QIIOUCQQHXE37GJF/https://www.debian.org/security/2020/dsa-4691
2020-05-19
Published