Bug 1840280 (CVE-2020-10995) - CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties to use recursive DNS services to attack third party authoritative name servers
Summary: CVE-2020-10995 pdns-recursor: issue in DNS protocol allows malicious parties ...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2020-10995
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1840281 1840282
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-26 16:54 UTC by Guilherme de Almeida Suckevicz
Modified: 2020-05-26 23:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 23:20:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-05-26 16:54:34 UTC
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.

Reference:
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2020-01.html

Comment 1 Guilherme de Almeida Suckevicz 2020-05-26 16:55:28 UTC
Created pdns-recursor tracking bugs for this issue:

Affects: epel-all [bug 1840281]
Affects: fedora-all [bug 1840282]

Comment 2 Product Security DevOps Team 2020-05-26 23:20:30 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.