CVE Vulnerabilities

CVE-2017-16910

Out-of-bounds Read

Published: Dec 07, 2018 | Modified: Dec 28, 2018
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
3.3 LOW
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Ubuntu
LOW

An error within the LibRaw::xtrans_interpolate() function (internal/dcraw_common.cpp) in LibRaw versions prior to 0.18.6 can be exploited to cause an invalid read memory access and subsequently a Denial of Service condition.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Libraw Libraw * 0.18.6 (excluding)
Darktable Ubuntu artful *
Darktable Ubuntu bionic *
Darktable Ubuntu cosmic *
Darktable Ubuntu devel *
Darktable Ubuntu disco *
Darktable Ubuntu eoan *
Darktable Ubuntu esm-apps/bionic *
Darktable Ubuntu esm-apps/focal *
Darktable Ubuntu esm-apps/jammy *
Darktable Ubuntu esm-apps/noble *
Darktable Ubuntu esm-apps/xenial *
Darktable Ubuntu focal *
Darktable Ubuntu groovy *
Darktable Ubuntu hirsute *
Darktable Ubuntu impish *
Darktable Ubuntu jammy *
Darktable Ubuntu kinetic *
Darktable Ubuntu lunar *
Darktable Ubuntu mantic *
Darktable Ubuntu noble *
Darktable Ubuntu oracular *
Darktable Ubuntu upstream *
Darktable Ubuntu xenial *
Darktable Ubuntu zesty *
Dcraw Ubuntu artful *
Dcraw Ubuntu bionic *
Dcraw Ubuntu cosmic *
Dcraw Ubuntu devel *
Dcraw Ubuntu disco *
Dcraw Ubuntu eoan *
Dcraw Ubuntu esm-apps/bionic *
Dcraw Ubuntu esm-apps/focal *
Dcraw Ubuntu esm-apps/jammy *
Dcraw Ubuntu esm-apps/noble *
Dcraw Ubuntu esm-apps/xenial *
Dcraw Ubuntu focal *
Dcraw Ubuntu groovy *
Dcraw Ubuntu hirsute *
Dcraw Ubuntu impish *
Dcraw Ubuntu jammy *
Dcraw Ubuntu kinetic *
Dcraw Ubuntu lunar *
Dcraw Ubuntu mantic *
Dcraw Ubuntu noble *
Dcraw Ubuntu oracular *
Dcraw Ubuntu trusty *
Dcraw Ubuntu upstream *
Dcraw Ubuntu xenial *
Dcraw Ubuntu zesty *
Exactimage Ubuntu artful *
Exactimage Ubuntu bionic *
Exactimage Ubuntu cosmic *
Exactimage Ubuntu devel *
Exactimage Ubuntu disco *
Exactimage Ubuntu eoan *
Exactimage Ubuntu esm-apps/bionic *
Exactimage Ubuntu esm-apps/focal *
Exactimage Ubuntu esm-apps/jammy *
Exactimage Ubuntu esm-apps/noble *
Exactimage Ubuntu esm-apps/xenial *
Exactimage Ubuntu focal *
Exactimage Ubuntu groovy *
Exactimage Ubuntu hirsute *
Exactimage Ubuntu impish *
Exactimage Ubuntu jammy *
Exactimage Ubuntu kinetic *
Exactimage Ubuntu lunar *
Exactimage Ubuntu mantic *
Exactimage Ubuntu noble *
Exactimage Ubuntu oracular *
Exactimage Ubuntu trusty *
Exactimage Ubuntu upstream *
Exactimage Ubuntu xenial *
Exactimage Ubuntu zesty *
Kodi Ubuntu artful *
Kodi Ubuntu zesty *
Libraw Ubuntu artful *
Libraw Ubuntu trusty *
Libraw Ubuntu xenial *
Libraw Ubuntu zesty *
Rawtherapee Ubuntu artful *
Rawtherapee Ubuntu bionic *
Rawtherapee Ubuntu cosmic *
Rawtherapee Ubuntu devel *
Rawtherapee Ubuntu disco *
Rawtherapee Ubuntu eoan *
Rawtherapee Ubuntu esm-apps/bionic *
Rawtherapee Ubuntu esm-apps/focal *
Rawtherapee Ubuntu esm-apps/jammy *
Rawtherapee Ubuntu esm-apps/noble *
Rawtherapee Ubuntu esm-apps/xenial *
Rawtherapee Ubuntu focal *
Rawtherapee Ubuntu groovy *
Rawtherapee Ubuntu hirsute *
Rawtherapee Ubuntu impish *
Rawtherapee Ubuntu jammy *
Rawtherapee Ubuntu kinetic *
Rawtherapee Ubuntu lunar *
Rawtherapee Ubuntu mantic *
Rawtherapee Ubuntu noble *
Rawtherapee Ubuntu oracular *
Rawtherapee Ubuntu trusty *
Rawtherapee Ubuntu upstream *
Rawtherapee Ubuntu xenial *
Rawtherapee Ubuntu zesty *
Ufraw Ubuntu artful *
Ufraw Ubuntu bionic *
Ufraw Ubuntu cosmic *
Ufraw Ubuntu disco *
Ufraw Ubuntu esm-apps/bionic *
Ufraw Ubuntu esm-apps/xenial *
Ufraw Ubuntu trusty *
Ufraw Ubuntu upstream *
Ufraw Ubuntu xenial *
Ufraw 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