Bug 1840182 (CVE-2020-10030) - CVE-2020-10030 pdns-recursor: stack-based out-of-bounds read via a larger hostname
Summary: CVE-2020-10030 pdns-recursor: stack-based out-of-bounds read via a larger hos...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2020-10030
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: 1840184 1840185
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-26 14:14 UTC by Guilherme de Almeida Suckevicz
Modified: 2020-05-26 15:15 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 15:15:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-05-26 14:14:14 UTC
An issue has been found in PowerDNS Recursor 4.1.0 up to and including 4.3.0. It allows an attacker (with enough privileges to change the system's hostname) to cause disclosure of uninitialized memory content via a stack-based out-of-bounds read. It only occurs on systems where gethostname() does not have '\0' termination of the returned string if the hostname is larger than the supplied buffer. (Linux systems are not affected because the buffer is always large enough. OpenBSD systems are not affected because the returned hostname always has '\0' termination.) Under some conditions, this issue can lead to the writing of one '\0' byte out-of-bounds on the stack, causing a denial of service or possibly arbitrary code execution.

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

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

Affects: epel-all [bug 1840185]
Affects: fedora-all [bug 1840184]

Comment 2 Product Security DevOps Team 2020-05-26 15:15:44 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.