CVE Vulnerabilities

CVE-2016-10195

Out-of-bounds Read

Published: Mar 15, 2017 | Modified: Jan 31, 2022
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
9.8 MODERATE
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

The name_parse function in evdns.c in libevent before 2.1.6-beta allows remote attackers to have unspecified impact via vectors involving the label_len variable, which triggers an out-of-bounds stack read.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Libevent Libevent_project * 2.1.5 (including)
Red Hat Enterprise Linux 6 RedHat firefox-0:52.1.0-2.el6_9 *
Red Hat Enterprise Linux 6 RedHat thunderbird-0:52.1.0-1.el6_9 *
Red Hat Enterprise Linux 7 RedHat firefox-0:52.1.0-2.el7_3 *
Red Hat Enterprise Linux 7 RedHat thunderbird-0:52.1.0-1.el7_3 *
Firefox Ubuntu devel *
Firefox Ubuntu precise *
Firefox Ubuntu trusty *
Firefox Ubuntu upstream *
Firefox Ubuntu xenial *
Firefox Ubuntu yakkety *
Firefox Ubuntu zesty *
Libevent Ubuntu devel *
Libevent Ubuntu precise *
Libevent Ubuntu trusty *
Libevent Ubuntu upstream *
Libevent Ubuntu xenial *
Libevent Ubuntu yakkety *
Libevent Ubuntu zesty *
Thunderbird Ubuntu devel *
Thunderbird Ubuntu trusty *
Thunderbird Ubuntu xenial *
Thunderbird Ubuntu yakkety *
Thunderbird Ubuntu zesty *

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