CVE Vulnerabilities

CVE-2019-1010190

Out-of-bounds Read

Published: Jul 24, 2019 | Modified: Apr 12, 2020
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.0/AV:L/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
5.6 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:H
Ubuntu
LOW

mgetty prior to 1.2.1 is affected by: out-of-bounds read. The impact is: DoS, the program may crash if the memory is not mapped. The component is: putwhitespan() in g3/pbm2g3.c. The attack vector is: Local, the victim must open a specially crafted file. The fixed version is: 1.2.1.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Mgetty Mgetty_project * 1.2.1 (excluding)
Mgetty Ubuntu bionic *
Mgetty Ubuntu devel *
Mgetty Ubuntu disco *
Mgetty Ubuntu eoan *
Mgetty Ubuntu esm-apps/bionic *
Mgetty Ubuntu esm-apps/focal *
Mgetty Ubuntu esm-apps/jammy *
Mgetty Ubuntu esm-apps/noble *
Mgetty Ubuntu esm-apps/xenial *
Mgetty Ubuntu focal *
Mgetty Ubuntu groovy *
Mgetty Ubuntu hirsute *
Mgetty Ubuntu impish *
Mgetty Ubuntu jammy *
Mgetty Ubuntu kinetic *
Mgetty Ubuntu lunar *
Mgetty Ubuntu mantic *
Mgetty Ubuntu noble *
Mgetty Ubuntu trusty *
Mgetty Ubuntu upstream *
Mgetty 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