CVE Vulnerabilities

CVE-2018-16855

Out-of-bounds Read

Published: Dec 03, 2018 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

An issue has been found in PowerDNS Recursor before version 4.1.8 where a remote attacker sending a DNS query can trigger an out-of-bounds memory read while computing the hash of the query for a packet cache lookup, possibly leading to a crash.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Recursor Powerdns * 4.1.8 (excluding)
Pdns-recursor Ubuntu bionic *
Pdns-recursor Ubuntu cosmic *
Pdns-recursor Ubuntu devel *
Pdns-recursor Ubuntu disco *
Pdns-recursor Ubuntu eoan *
Pdns-recursor Ubuntu esm-apps/bionic *
Pdns-recursor Ubuntu focal *
Pdns-recursor Ubuntu groovy *
Pdns-recursor Ubuntu hirsute *
Pdns-recursor Ubuntu impish *
Pdns-recursor Ubuntu jammy *
Pdns-recursor Ubuntu kinetic *
Pdns-recursor Ubuntu lunar *
Pdns-recursor Ubuntu mantic *
Pdns-recursor Ubuntu noble *
Pdns-recursor Ubuntu oracular *
Pdns-recursor Ubuntu upstream *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References