CVE Vulnerabilities

CVE-2019-17263

Out-of-bounds Read

Published: Oct 06, 2019 | Modified: Jun 18, 2024
CVSS 3.x
3.3
LOW
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

In libyal libfwsi before 20191006, libfwsi_extension_block_copy_from_byte_stream in libfwsi_extension_block.c has a heap-based buffer over-read because rejection of an unsupported size only considers values less than 6, even though values of 6 and 7 are also unsupported. NOTE: the vendor has disputed this as described in the GitHub issue

Weakness

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

Affected Software

Name Vendor Start Version End Version
Libfwsi Libfwsi_project * 20191006 (excluding)
Libfwsi Ubuntu bionic *
Libfwsi Ubuntu disco *
Libfwsi Ubuntu eoan *
Libfwsi Ubuntu groovy *
Libfwsi Ubuntu hirsute *
Libfwsi Ubuntu impish *
Libfwsi Ubuntu kinetic *
Libfwsi Ubuntu lunar *
Libfwsi Ubuntu mantic *
Libfwsi Ubuntu trusty *
Libfwsi Ubuntu xenial *
Liblnk Ubuntu bionic *
Liblnk Ubuntu disco *
Liblnk Ubuntu eoan *
Liblnk Ubuntu groovy *
Liblnk Ubuntu hirsute *
Liblnk Ubuntu impish *
Liblnk Ubuntu kinetic *
Liblnk Ubuntu lunar *
Liblnk Ubuntu mantic *
Liblnk Ubuntu trusty *
Liblnk 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