CVE Vulnerabilities

CVE-2019-12360

Out-of-bounds Read

Published: May 27, 2019 | Modified: Nov 07, 2023
CVSS 3.x
7.1
HIGH
Source:
NVD
CVSS:3.0/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
RedHat/V3
7.1 MODERATE
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Ubuntu
LOW

A stack-based buffer over-read exists in FoFiTrueType::dumpString in fofi/FoFiTrueType.cc in Xpdf 4.01.01. It can, for example, be triggered by sending crafted TrueType data in a PDF document to the pdftops tool. It might allow an attacker to cause Denial of Service or leak memory data into dump content.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Xpdfreader Glyphandcog 4.01.01 (including) 4.01.01 (including)
Emscripten Ubuntu bionic *
Emscripten Ubuntu cosmic *
Emscripten Ubuntu devel *
Emscripten Ubuntu disco *
Emscripten Ubuntu eoan *
Emscripten Ubuntu esm-apps/bionic *
Emscripten Ubuntu esm-apps/jammy *
Emscripten Ubuntu esm-apps/noble *
Emscripten Ubuntu esm-apps/xenial *
Emscripten Ubuntu hirsute *
Emscripten Ubuntu impish *
Emscripten Ubuntu jammy *
Emscripten Ubuntu kinetic *
Emscripten Ubuntu lunar *
Emscripten Ubuntu mantic *
Emscripten Ubuntu noble *
Emscripten Ubuntu oracular *
Emscripten Ubuntu trusty *
Emscripten Ubuntu xenial *
Ipe Ubuntu cosmic *
Libextractor Ubuntu cosmic *
Poppler Ubuntu trusty *
Texlive-bin Ubuntu bionic *
Texlive-bin Ubuntu cosmic *
Texlive-bin Ubuntu disco *
Texlive-bin Ubuntu eoan *
Texlive-bin Ubuntu groovy *
Texlive-bin Ubuntu hirsute *
Texlive-bin Ubuntu impish *
Texlive-bin Ubuntu kinetic *
Texlive-bin Ubuntu lunar *
Texlive-bin Ubuntu mantic *
Texlive-bin Ubuntu trusty *
Texlive-bin Ubuntu xenial *
Utopia-documents Ubuntu trusty *
Xpdf Ubuntu cosmic *
Xpdf Ubuntu disco *
Xpdf Ubuntu eoan *
Xpdf Ubuntu hirsute *
Xpdf Ubuntu impish *
Xpdf Ubuntu trusty *
Xpdf Ubuntu xenial *

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