CVE Vulnerabilities

CVE-2017-6962

Integer Overflow or Wraparound

Published: Mar 17, 2017 | Modified: Mar 20, 2017
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

An issue was discovered in apng2gif 1.7. There is an integer overflow resulting in a heap-based buffer overflow. This is related to the read_chunk function making an unchecked addition of 12.

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
Apng2gif Apng2gif_project 1.7 (including) 1.7 (including)
Apng2gif Ubuntu artful *
Apng2gif Ubuntu bionic *
Apng2gif Ubuntu cosmic *
Apng2gif Ubuntu devel *
Apng2gif Ubuntu disco *
Apng2gif Ubuntu eoan *
Apng2gif Ubuntu esm-apps/bionic *
Apng2gif Ubuntu focal *
Apng2gif Ubuntu groovy *
Apng2gif Ubuntu hirsute *
Apng2gif Ubuntu impish *
Apng2gif Ubuntu jammy *
Apng2gif Ubuntu kinetic *
Apng2gif Ubuntu lunar *
Apng2gif Ubuntu mantic *
Apng2gif Ubuntu noble *
Apng2gif Ubuntu oracular *
Apng2gif Ubuntu precise *
Apng2gif Ubuntu trusty *
Apng2gif Ubuntu upstream *
Apng2gif Ubuntu yakkety *
Apng2gif Ubuntu zesty *

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