CVE Vulnerabilities

CVE-2020-27842

Out-of-bounds Read

Published: Jan 05, 2021 | Modified: Nov 07, 2023
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/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.5 LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

Theres a flaw in openjpegs t2 encoder in versions prior to 2.4.0. An attacker who is able to provide crafted input to be processed by openjpeg could cause a null pointer dereference. The highest impact of this flaw is to application availability.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Openjpeg Uclouvain * 2.4.0 (excluding)
Red Hat Enterprise Linux 8 RedHat openjpeg2-0:2.4.0-4.el8 *
Blender Ubuntu bionic *
Blender Ubuntu groovy *
Blender Ubuntu hirsute *
Blender Ubuntu impish *
Blender Ubuntu kinetic *
Blender Ubuntu lunar *
Blender Ubuntu mantic *
Blender Ubuntu trusty *
Blender Ubuntu xenial *
Ghostscript Ubuntu bionic *
Ghostscript Ubuntu trusty *
Ghostscript Ubuntu xenial *
Insighttoolkit4 Ubuntu bionic *
Insighttoolkit4 Ubuntu groovy *
Insighttoolkit4 Ubuntu hirsute *
Insighttoolkit4 Ubuntu impish *
Insighttoolkit4 Ubuntu kinetic *
Insighttoolkit4 Ubuntu lunar *
Insighttoolkit4 Ubuntu trusty *
Insighttoolkit4 Ubuntu xenial *
Openjpeg Ubuntu esm-apps/xenial *
Openjpeg Ubuntu esm-infra-legacy/trusty *
Openjpeg Ubuntu trusty *
Openjpeg Ubuntu trusty/esm *
Openjpeg Ubuntu xenial *
Openjpeg2 Ubuntu bionic *
Openjpeg2 Ubuntu devel *
Openjpeg2 Ubuntu esm-apps/xenial *
Openjpeg2 Ubuntu focal *
Openjpeg2 Ubuntu groovy *
Openjpeg2 Ubuntu hirsute *
Openjpeg2 Ubuntu impish *
Openjpeg2 Ubuntu jammy *
Openjpeg2 Ubuntu kinetic *
Openjpeg2 Ubuntu lunar *
Openjpeg2 Ubuntu mantic *
Openjpeg2 Ubuntu noble *
Openjpeg2 Ubuntu oracular *
Openjpeg2 Ubuntu upstream *
Openjpeg2 Ubuntu xenial *
Qtwebengine-opensource-src Ubuntu bionic *
Qtwebengine-opensource-src Ubuntu groovy *
Qtwebengine-opensource-src Ubuntu hirsute *
Qtwebengine-opensource-src Ubuntu impish *
Qtwebengine-opensource-src Ubuntu kinetic *
Qtwebengine-opensource-src Ubuntu lunar *
Qtwebengine-opensource-src Ubuntu mantic *
Texmaker Ubuntu bionic *
Texmaker Ubuntu groovy *
Texmaker Ubuntu hirsute *
Texmaker Ubuntu impish *
Texmaker Ubuntu kinetic *
Texmaker Ubuntu lunar *
Texmaker Ubuntu mantic *
Texmaker Ubuntu trusty *
Texmaker 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