CVE Vulnerabilities

CVE-2020-12135

Integer Overflow or Wraparound

Published: Apr 24, 2020 | Modified: Aug 12, 2020
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 MODERATE
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

bson before 0.8 incorrectly uses int rather than size_t for many variables, parameters, and return values. In particular, the bson_ensure_space() parameter bytesNeeded could have an integer overflow via properly constructed bson input.

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
Whoopsie Whoopsie_project * 0.2.69 (including)
Duo-unix Ubuntu bionic *
Duo-unix Ubuntu eoan *
Duo-unix Ubuntu groovy *
Duo-unix Ubuntu hirsute *
Duo-unix Ubuntu impish *
Duo-unix Ubuntu kinetic *
Duo-unix Ubuntu lunar *
Duo-unix Ubuntu mantic *
Duo-unix Ubuntu trusty *
Duo-unix Ubuntu xenial *
Whoopsie Ubuntu bionic *
Whoopsie Ubuntu devel *
Whoopsie Ubuntu eoan *
Whoopsie Ubuntu focal *
Whoopsie Ubuntu groovy *
Whoopsie Ubuntu hirsute *
Whoopsie Ubuntu impish *
Whoopsie Ubuntu jammy *
Whoopsie Ubuntu kinetic *
Whoopsie Ubuntu lunar *
Whoopsie Ubuntu mantic *
Whoopsie Ubuntu noble *
Whoopsie Ubuntu trusty *
Whoopsie 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