CVE Vulnerabilities

CVE-2021-41991

Integer Overflow or Wraparound

Published: Oct 18, 2021 | Modified: Nov 07, 2023
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/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
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

The in-memory certificate cache in strongSwan before 5.9.4 has a remote integer overflow upon receiving many requests with different certificates to fill the cache and later trigger the replacement of cache entries. The code attempts to select a less-often-used cache entry by means of a random number generator, but this is not done correctly. Remote code execution might be a slight possibility.

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
Strongswan Strongswan 4.2.10 (including) 5.9.4 (excluding)
Strongswan Ubuntu bionic *
Strongswan Ubuntu devel *
Strongswan Ubuntu esm-infra/xenial *
Strongswan Ubuntu fips-preview/jammy *
Strongswan Ubuntu fips-updates/bionic *
Strongswan Ubuntu fips-updates/focal *
Strongswan Ubuntu fips-updates/jammy *
Strongswan Ubuntu fips-updates/xenial *
Strongswan Ubuntu fips/bionic *
Strongswan Ubuntu fips/focal *
Strongswan Ubuntu fips/xenial *
Strongswan Ubuntu focal *
Strongswan Ubuntu hirsute *
Strongswan Ubuntu impish *
Strongswan Ubuntu jammy *
Strongswan Ubuntu kinetic *
Strongswan Ubuntu lunar *
Strongswan Ubuntu mantic *
Strongswan Ubuntu noble *
Strongswan Ubuntu oracular *
Strongswan Ubuntu trusty *
Strongswan Ubuntu trusty/esm *
Strongswan 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