CVE Vulnerabilities

CVE-2022-22721

Integer Overflow or Wraparound

Published: Mar 14, 2022 | Modified: Nov 07, 2023
CVSS 3.x
9.1
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
CVSS 2.x
5.8 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:P
RedHat/V2
RedHat/V3
7.4 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
Ubuntu
LOW

If LimitXMLRequestBody is set to allow request bodies larger than 350MB (defaults to 1M) on 32 bit systems an integer overflow happens which later causes out of bounds writes. This issue affects Apache HTTP Server 2.4.52 and earlier.

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
Http_server Apache * 2.4.52 (including)
JBoss Core Services for RHEL 8 RedHat jbcs-httpd24-httpd-0:2.4.51-37.el8jbcs *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-httpd-0:2.4.51-37.el7jbcs *
Red Hat Enterprise Linux 8 RedHat httpd:2.4-8070020220725152258.3b9f49c4 *
Red Hat Enterprise Linux 9 RedHat httpd-0:2.4.53-7.el9 *
Red Hat JBoss Core Services 1 RedHat jbcs-httpd24-httpd *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat httpd24-httpd-0:2.4.34-23.el7.5 *
Apache2 Ubuntu bionic *
Apache2 Ubuntu devel *
Apache2 Ubuntu esm-infra/bionic *
Apache2 Ubuntu esm-infra/xenial *
Apache2 Ubuntu focal *
Apache2 Ubuntu impish *
Apache2 Ubuntu jammy *
Apache2 Ubuntu trusty *
Apache2 Ubuntu trusty/esm *
Apache2 Ubuntu upstream *
Apache2 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