CVE Vulnerabilities


Integer Overflow or Wraparound

Published: Nov 21, 2012 | Modified: Aug 06, 2020
CVSS 3.x
CVSS 2.x

Integer overflow in the WebGL subsystem in Mozilla Firefox before 17.0, Firefox ESR 10.x before 10.0.11, Thunderbird before 17.0, Thunderbird ESR 10.x before 10.0.11, and SeaMonkey before 2.14 allows remote attackers to execute arbitrary code or cause a denial of service (invalid write operation) via crafted data.


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
Firefox Mozilla * *
Firefox_esr Mozilla * *
Seamonkey Mozilla * *
Thunderbird Mozilla * *
Thunderbird_esr Mozilla * *
Red Hat Enterprise Linux 5 RedHat firefox-0:10.0.11-1.el5_8 *
Red Hat Enterprise Linux 5 RedHat xulrunner-0:10.0.11-1.el5_8 *
Red Hat Enterprise Linux 5 RedHat thunderbird-0:10.0.11-1.el5_8 *
Red Hat Enterprise Linux 6 RedHat firefox-0:10.0.11-1.el6_3 *
Red Hat Enterprise Linux 6 RedHat xulrunner-0:10.0.11-1.el6_3 *
Red Hat Enterprise Linux 6 RedHat thunderbird-0:10.0.11-1.el6_3 *
Firefox Ubuntu hardy *
Firefox Ubuntu lucid *
Firefox Ubuntu oneiric *
Firefox Ubuntu precise *
Firefox Ubuntu quantal *
Seamonkey Ubuntu hardy *
Seamonkey Ubuntu lucid *
Seamonkey Ubuntu oneiric *
Thunderbird Ubuntu hardy *
Thunderbird Ubuntu lucid *
Thunderbird Ubuntu oneiric *
Thunderbird Ubuntu precise *
Thunderbird Ubuntu quantal *
Xulrunner-1.9.2 Ubuntu hardy *
Xulrunner-1.9.2 Ubuntu lucid *

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.