CVE Vulnerabilities


Integer Overflow or Wraparound

Published: Feb 12, 2020 | Modified: Feb 14, 2020
CVSS 3.x
CVSS 2.x

Integer overflow in the LZO algorithm variant in Oberhumer liblzo2 and lzo-2 before 2.07 on 32-bit platforms might allow remote attackers to execute arbitrary code via a crafted Literal Run.


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
Liblzo2 Oberhumer * *
Lzo2 Oberhumer * *
Red Hat Enterprise Linux 6 RedHat lzo-0:2.03-3.1.el6_5.1 *
Red Hat Enterprise Linux 7 RedHat lzo-0:2.06-6.el7_0.2 *
Grub2 Ubuntu bionic *
Grub2 Ubuntu devel *
Grub2 Ubuntu focal *
Grub2 Ubuntu groovy *
Grub2 Ubuntu hirsute *
Grub2 Ubuntu impish *
Grub2 Ubuntu jammy *
Grub2 Ubuntu kinetic *
Grub2 Ubuntu lunar *
Grub2 Ubuntu precise/esm *
Grub2 Ubuntu trusty *
Grub2 Ubuntu xenial *
Grub2-signed Ubuntu devel *
Grub2-signed Ubuntu focal *
Grub2-signed Ubuntu groovy *
Grub2-signed Ubuntu hirsute *
Grub2-signed Ubuntu impish *
Grub2-signed Ubuntu jammy *
Grub2-signed Ubuntu kinetic *
Grub2-signed Ubuntu lunar *
Grub2-signed Ubuntu trusty *
Grub2-signed Ubuntu xenial *
Krfb Ubuntu bionic *
Krfb Ubuntu devel *
Krfb Ubuntu esm-apps/bionic *
Krfb Ubuntu esm-apps/focal *
Krfb Ubuntu esm-apps/jammy *
Krfb Ubuntu esm-apps/xenial *
Krfb Ubuntu focal *
Krfb Ubuntu groovy *
Krfb Ubuntu hirsute *
Krfb Ubuntu impish *
Krfb Ubuntu jammy *
Krfb Ubuntu kinetic *
Krfb Ubuntu lunar *
Krfb Ubuntu trusty *
Krfb Ubuntu upstream *
Krfb Ubuntu xenial *
Lzo2 Ubuntu bionic *
Lzo2 Ubuntu devel *
Lzo2 Ubuntu esm-infra/bionic *
Lzo2 Ubuntu esm-infra/xenial *
Lzo2 Ubuntu focal *
Lzo2 Ubuntu groovy *
Lzo2 Ubuntu hirsute *
Lzo2 Ubuntu impish *
Lzo2 Ubuntu jammy *
Lzo2 Ubuntu kinetic *
Lzo2 Ubuntu lucid *
Lzo2 Ubuntu lunar *
Lzo2 Ubuntu precise *
Lzo2 Ubuntu precise/esm *
Lzo2 Ubuntu saucy *
Lzo2 Ubuntu trusty *
Lzo2 Ubuntu trusty/esm *
Lzo2 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.