CVE Vulnerabilities

CVE-2019-17546

Integer Overflow or Wraparound

Published: Oct 14, 2019 | Modified: Nov 07, 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
8.8 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

tif_getimage.c in LibTIFF through 4.0.10, as used in GDAL through 3.0.1 and other products, has an integer overflow that potentially causes a heap-based buffer overflow via a crafted RGBA image, related to a Negative-size-param condition.

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
Libtiff Libtiff * 4.1.0 (excluding)
Red Hat Enterprise Linux 7 RedHat libtiff-0:4.0.3-35.el7 *
Red Hat Enterprise Linux 8 RedHat libtiff-0:4.0.9-18.el8 *
Chromium-browser Ubuntu disco *
Chromium-browser Ubuntu trusty *
Chromium-browser Ubuntu upstream *
Gdal Ubuntu esm-apps/xenial *
Gdal Ubuntu trusty *
Gdal Ubuntu trusty/esm *
Gdal Ubuntu xenial *
Neuron Ubuntu bionic *
Neuron Ubuntu disco *
Neuron Ubuntu eoan *
Neuron Ubuntu groovy *
Neuron Ubuntu hirsute *
Neuron Ubuntu impish *
Neuron Ubuntu kinetic *
Neuron Ubuntu trusty *
Qt4-x11 Ubuntu trusty *
Qtimageformats-opensource-src Ubuntu bionic *
Qtimageformats-opensource-src Ubuntu disco *
Qtimageformats-opensource-src Ubuntu eoan *
Qtimageformats-opensource-src Ubuntu groovy *
Qtimageformats-opensource-src Ubuntu hirsute *
Qtimageformats-opensource-src Ubuntu impish *
Qtimageformats-opensource-src Ubuntu kinetic *
Qtimageformats-opensource-src Ubuntu lunar *
Qtimageformats-opensource-src Ubuntu trusty *
Qtimageformats-opensource-src Ubuntu xenial *
Qtwebengine-opensource-src Ubuntu bionic *
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 *
Texmaker Ubuntu bionic *
Texmaker Ubuntu disco *
Texmaker Ubuntu eoan *
Texmaker Ubuntu groovy *
Texmaker Ubuntu hirsute *
Texmaker Ubuntu impish *
Texmaker Ubuntu kinetic *
Texmaker Ubuntu lunar *
Tiff Ubuntu bionic *
Tiff Ubuntu disco *
Tiff Ubuntu esm-infra/bionic *
Tiff Ubuntu esm-infra/xenial *
Tiff Ubuntu precise/esm *
Tiff Ubuntu trusty *
Tiff Ubuntu trusty/esm *
Tiff Ubuntu upstream *
Tiff 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