CVE Vulnerabilities

CVE-2008-4864

Integer Overflow or Wraparound

Published: Nov 01, 2008 | Modified: Jul 05, 2022
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

Multiple integer overflows in imageop.c in the imageop module in Python 1.5.2 through 2.5.1 allow context-dependent attackers to break out of the Python VM and execute arbitrary code via large integer values in certain arguments to the crop function, leading to a buffer overflow, a different vulnerability than CVE-2007-4965 and CVE-2008-1679.

Weakness

The software 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
Python Python 2.5.0 *
Python Python 1.5.2 *
Red Hat Enterprise Linux 3 RedHat python-0:2.2.3-6.11 *
Red Hat Enterprise Linux 4 RedHat python-0:2.3.4-14.7.el4_8.2 *
Red Hat Enterprise Linux 5 RedHat python-0:2.4.3-24.el5_3.6 *
Python2.2 Ubuntu dapper *
Python2.3 Ubuntu dapper *
Python2.4 Ubuntu dapper *
Python2.4 Ubuntu gutsy *
Python2.4 Ubuntu hardy *
Python2.4 Ubuntu intrepid *
Python2.4 Ubuntu upstream *
Python2.5 Ubuntu gutsy *
Python2.5 Ubuntu hardy *
Python2.5 Ubuntu upstream *

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