CVE-2020-10995
Published: 19 May 2020
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.
Priority
Status
Package | Release | Status |
---|---|---|
pdns-recursor Launchpad, Ubuntu, Debian |
impish |
Not vulnerable
(4.3.1-1)
|
focal |
Needs triage
|
|
hirsute |
Not vulnerable
(4.3.1-1)
|
|
xenial |
Needs triage
|
|
jammy |
Not vulnerable
(4.3.1-1)
|
|
kinetic |
Not vulnerable
(4.3.1-1)
|
|
lunar |
Not vulnerable
(4.3.1-1)
|
|
bionic |
Needs triage
|
|
eoan |
Ignored
(end of life)
|
|
groovy |
Not vulnerable
(4.3.1-1)
|
|
trusty |
Does not exist
|
|
upstream |
Needs triage
|
|
mantic |
Not vulnerable
(4.3.1-1)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.5 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | None |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |