CVE Vulnerabilities

CVE-2019-5608

Out-of-bounds Read

Published: Aug 30, 2019 | Modified: Jan 31, 2023
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

In FreeBSD 12.0-STABLE before r350648, 12.0-RELEASE before 12.0-RELEASE-p9, 11.3-STABLE before r350650, 11.3-RELEASE before 11.3-RELEASE-p2, and 11.2-RELEASE before 11.2-RELEASE-p13, the ICMPv6 input path incorrectly handles cases where an MLDv2 listener query packet is internally fragmented across multiple mbufs. A remote attacker may be able to cause an out-of-bounds read or write that may cause the kernel to attempt to access an unmapped page and subsequently panic.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Freebsd Freebsd 11.2 (including) 11.2 (including)
Freebsd Freebsd 11.2-p10 (including) 11.2-p10 (including)
Freebsd Freebsd 11.2-p11 (including) 11.2-p11 (including)
Freebsd Freebsd 11.2-p12 (including) 11.2-p12 (including)
Freebsd Freebsd 11.2-p13 (including) 11.2-p13 (including)
Freebsd Freebsd 11.2-p2 (including) 11.2-p2 (including)
Freebsd Freebsd 11.2-p3 (including) 11.2-p3 (including)
Freebsd Freebsd 11.2-p4 (including) 11.2-p4 (including)
Freebsd Freebsd 11.2-p5 (including) 11.2-p5 (including)
Freebsd Freebsd 11.2-p6 (including) 11.2-p6 (including)
Freebsd Freebsd 11.2-p7 (including) 11.2-p7 (including)
Freebsd Freebsd 11.2-p8 (including) 11.2-p8 (including)
Freebsd Freebsd 11.2-p9 (including) 11.2-p9 (including)
Freebsd Freebsd 11.3 (including) 11.3 (including)
Freebsd Freebsd 11.3-p1 (including) 11.3-p1 (including)
Freebsd Freebsd 11.3-p2 (including) 11.3-p2 (including)
Freebsd Freebsd 11.3-p3 (including) 11.3-p3 (including)
Freebsd Freebsd 12.0 (including) 12.0 (including)
Freebsd Freebsd 12.0-p1 (including) 12.0-p1 (including)
Freebsd Freebsd 12.0-p3 (including) 12.0-p3 (including)
Freebsd Freebsd 12.0-p4 (including) 12.0-p4 (including)
Freebsd Freebsd 12.0-p5 (including) 12.0-p5 (including)
Freebsd Freebsd 12.0-p8 (including) 12.0-p8 (including)

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