Bug 1649028 (CVE-2018-14626) - CVE-2018-14626 pdns: Packet cache pollution via crafted query
Summary: CVE-2018-14626 pdns: Packet cache pollution via crafted query
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2018-14626
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: 1649029 1649030
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-12 18:27 UTC by Pedro Sampaio
Modified: 2019-09-29 15:02 UTC (History)
3 users (show)

Fixed In Version: pdns-recursor 4.1.5, pdns-recursor 4.0.9, pdns 4.1.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:42:27 UTC
Embargoed:


Attachments (Terms of Use)

Description Pedro Sampaio 2018-11-12 18:27:20 UTC
An issue has been found in PowerDNS Authoritative Server allowing a
remote user to craft a DNS query that will cause an answer without DNSSEC
records to be inserted into the packet cache and be returned to clients
asking for DNSSEC records, thus hiding the presence of DNSSEC signatures
for a specific qname and qtype.

For a DNSSEC-signed domain, this means that DNSSEC validating clients
will consider the answer to be bogus until it expires from the packet
cache, leading to a denial of service.

References:

https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2018-06.html
https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2018-05.html

Comment 1 Pedro Sampaio 2018-11-12 18:28:05 UTC
Created pdns tracking bugs for this issue:

Affects: epel-all [bug 1649030]
Affects: fedora-all [bug 1649029]

Comment 2 Product Security DevOps Team 2019-06-10 10:42:27 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.