CVE Vulnerabilities

CVE-2017-12425

Integer Overflow or Wraparound

Published: Aug 04, 2017 | Modified: Aug 02, 2022
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.0/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
Ubuntu

An issue was discovered in Varnish HTTP Cache 4.0.1 through 4.0.4, 4.1.0 through 4.1.7, 5.0.0, and 5.1.0 through 5.1.2. A wrong if statement in the varnishd source code means that particular invalid requests from the client can trigger an assert, related to an Integer Overflow. This causes the varnishd worker process to abort and restart, losing the cached contents in the process. An attacker can therefore crash the varnishd worker process on demand and effectively keep it from serving content - a Denial-of-Service attack. The specific source-code filename containing the incorrect statement varies across releases.

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
Varnish Varnish-cache 4.0.2-rc-1 (including) 4.0.2-rc-1 (including)
Varnish Varnish-cache 4.0.3-rc-1 (including) 4.0.3-rc-1 (including)
Varnish Varnish-cache 4.0.3-rc-2 (including) 4.0.3-rc-2 (including)
Varnish Varnish-cache 4.0.3-rc-2-proper (including) 4.0.3-rc-2-proper (including)
Varnish Varnish-cache 4.0.3-rc-3 (including) 4.0.3-rc-3 (including)
Varnish_cache Varnish_cache_project 4.0.1 (including) 4.0.1 (including)
Varnish_cache Varnish_cache_project 4.0.2 (including) 4.0.2 (including)
Varnish_cache Varnish_cache_project 4.0.3 (including) 4.0.3 (including)
Varnish_cache Varnish_cache_project 4.0.4 (including) 4.0.4 (including)

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