CVE Vulnerabilities

CVE-2016-10165

Out-of-bounds Read

Published: Feb 03, 2017 | Modified: Jan 10, 2024
CVSS 3.x
7.1
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
CVSS 2.x
5.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:P
RedHat/V2
5.8 MODERATE
AV:N/AC:M/Au:N/C:P/I:N/A:P
RedHat/V3
7.1 MODERATE
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Ubuntu
LOW

The Type_MLU_Read function in cmstypes.c in Little CMS (aka lcms2) allows remote attackers to obtain sensitive information or cause a denial of service via an image with a crafted ICC profile, which triggers an out-of-bounds heap 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
Little_cms_color_engine Littlecms * 2.11 (excluding)
Oracle Java for Red Hat Enterprise Linux 6 RedHat java-1.8.0-oracle-1:1.8.0.151-1jpp.1.el6 *
Oracle Java for Red Hat Enterprise Linux 6 RedHat java-1.7.0-oracle-1:1.7.0.161-1jpp.3.el6 *
Oracle Java for Red Hat Enterprise Linux 7 RedHat java-1.8.0-oracle-1:1.8.0.151-1jpp.5.el7 *
Oracle Java for Red Hat Enterprise Linux 7 RedHat java-1.7.0-oracle-1:1.7.0.161-1jpp.4.el7 *
Red Hat Enterprise Linux 5 RedHat java-1.7.0-openjdk-1:1.7.0.121-2.6.8.1.el5_11 *
Red Hat Enterprise Linux 6 RedHat java-1.8.0-openjdk-1:1.8.0.111-0.b15.el6_8 *
Red Hat Enterprise Linux 6 RedHat java-1.7.0-openjdk-1:1.7.0.121-2.6.8.1.el6_8 *
Red Hat Enterprise Linux 6 Supplementary RedHat java-1.8.0-ibm-1:1.8.0.5.5-1jpp.1.el6_9 *
Red Hat Enterprise Linux 6 Supplementary RedHat java-1.7.1-ibm-1:1.7.1.4.15-1jpp.3.el6_9 *
Red Hat Enterprise Linux 7 RedHat java-1.8.0-openjdk-1:1.8.0.111-1.b15.el7_2 *
Red Hat Enterprise Linux 7 RedHat java-1.7.0-openjdk-1:1.7.0.121-2.6.8.0.el7_3 *
Red Hat Enterprise Linux 7 Supplementary RedHat java-1.8.0-ibm-1:1.8.0.5.5-1jpp.2.el7 *
Red Hat Enterprise Linux 7 Supplementary RedHat java-1.7.1-ibm-1:1.7.1.4.15-1jpp.2.el7 *
Red Hat Satellite 5.8 RedHat java-1.8.0-ibm-1:1.8.0.5.5-1jpp.1.el6_9 *
Red Hat Satellite 5.8 ELS RedHat java-1.8.0-ibm-1:1.8.0.5.5-1jpp.1.el6_9 *
Lcms2 Ubuntu artful *
Lcms2 Ubuntu bionic *
Lcms2 Ubuntu devel *
Lcms2 Ubuntu precise *
Lcms2 Ubuntu trusty *
Lcms2 Ubuntu upstream *
Lcms2 Ubuntu vivid/stable-phone-overlay *
Lcms2 Ubuntu xenial *
Lcms2 Ubuntu yakkety *
Lcms2 Ubuntu zesty *
Openjdk-7 Ubuntu precise *
Openjdk-7 Ubuntu trusty *

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