CVE Vulnerabilities

CVE-2018-20847

Integer Overflow or Wraparound

Published: Jun 26, 2019 | Modified: Feb 27, 2023
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
4 LOW
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Ubuntu
MEDIUM

An improper computation of p_tx0, p_tx1, p_ty0 and p_ty1 in the function opj_get_encoding_parameters in openjp2/pi.c in OpenJPEG through 2.3.0 can lead to an integer overflow.

Weakness

The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.

Affected Software

Name Vendor Start Version End Version
Openjpeg Uclouvain * 2.3.0 (including)
Red Hat Enterprise Linux 8 RedHat openjpeg2-0:2.4.0-4.el8 *
Blender Ubuntu bionic *
Blender Ubuntu cosmic *
Blender Ubuntu disco *
Blender Ubuntu eoan *
Blender Ubuntu groovy *
Blender Ubuntu hirsute *
Blender Ubuntu impish *
Blender Ubuntu kinetic *
Blender Ubuntu lunar *
Blender Ubuntu mantic *
Blender Ubuntu trusty *
Blender Ubuntu xenial *
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 *
Gdcm Ubuntu cosmic *
Gdcm Ubuntu trusty *
Insighttoolkit4 Ubuntu bionic *
Insighttoolkit4 Ubuntu cosmic *
Insighttoolkit4 Ubuntu disco *
Insighttoolkit4 Ubuntu eoan *
Insighttoolkit4 Ubuntu groovy *
Insighttoolkit4 Ubuntu hirsute *
Insighttoolkit4 Ubuntu impish *
Insighttoolkit4 Ubuntu kinetic *
Insighttoolkit4 Ubuntu lunar *
Insighttoolkit4 Ubuntu trusty *
Insighttoolkit4 Ubuntu xenial *
Openjpeg Ubuntu upstream *
Openjpeg2 Ubuntu cosmic *
Openjpeg2 Ubuntu trusty *
Openjpeg2 Ubuntu upstream *
Openjpeg2 Ubuntu xenial *
Qtwebengine-opensource-src Ubuntu bionic *
Qtwebengine-opensource-src Ubuntu cosmic *
Qtwebengine-opensource-src Ubuntu disco *
Qtwebengine-opensource-src Ubuntu eoan *
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 cosmic *
Texmaker Ubuntu disco *
Texmaker Ubuntu eoan *
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

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
  • Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
  • Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
  • Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
  • Understand the programming language’s underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, “not-a-number” calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
  • Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.

References