CVE-2015-3416

The sqlite3VXPrintf function in printf.c in SQLite before 3.8.9 does not properly handle precision and width values during floating-point conversions, which allows context-dependent attackers to cause a denial of service (integer overflow and stack-based buffer overflow) or possibly have unspecified other impact via large integers in a crafted printf function call in a SELECT statement.

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
Ubuntu_linux	Canonical	12.04 (including)	12.04 (including)
Ubuntu_linux	Canonical	14.04 (including)	14.04 (including)
Ubuntu_linux	Canonical	15.04 (including)	15.04 (including)
Red Hat Enterprise Linux 6	RedHat	sqlite-0:3.6.20-1.el6_7.2	*
Red Hat Enterprise Linux 7	RedHat	sqlite-0:3.7.17-6.el7_1.1	*
Sqlite	Ubuntu	artful	*
Sqlite	Ubuntu	bionic	*
Sqlite	Ubuntu	cosmic	*
Sqlite	Ubuntu	disco	*
Sqlite	Ubuntu	eoan	*
Sqlite	Ubuntu	esm-apps/bionic	*
Sqlite	Ubuntu	esm-apps/focal	*
Sqlite	Ubuntu	esm-apps/jammy	*
Sqlite	Ubuntu	esm-apps/xenial	*
Sqlite	Ubuntu	esm-infra-legacy/trusty	*
Sqlite	Ubuntu	focal	*
Sqlite	Ubuntu	groovy	*
Sqlite	Ubuntu	hirsute	*
Sqlite	Ubuntu	impish	*
Sqlite	Ubuntu	jammy	*
Sqlite	Ubuntu	kinetic	*
Sqlite	Ubuntu	lucid	*
Sqlite	Ubuntu	precise	*
Sqlite	Ubuntu	trusty	*
Sqlite	Ubuntu	trusty/esm	*
Sqlite	Ubuntu	upstream	*
Sqlite	Ubuntu	utopic	*
Sqlite	Ubuntu	vivid	*
Sqlite	Ubuntu	wily	*
Sqlite	Ubuntu	xenial	*
Sqlite	Ubuntu	yakkety	*
Sqlite	Ubuntu	zesty	*
Sqlite3	Ubuntu	lucid	*
Sqlite3	Ubuntu	precise	*
Sqlite3	Ubuntu	trusty	*
Sqlite3	Ubuntu	upstream	*
Sqlite3	Ubuntu	utopic	*
Sqlite3	Ubuntu	vivid	*
Sqlite3	Ubuntu	vivid/stable-phone-overlay	*
Sqlite3	Ubuntu	vivid/ubuntu-core	*

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.

https://cwe.mitre.org/data/definitions/92.html

NVD	https://nvd.nist.gov/vuln/detail/CVE-2015-3416
CWE	https://cwe.mitre.org/data/definitions/190.html

Integer Overflow or Wraparound

Weakness

Affected Software

Potential Mitigations

References

CVE-2015-3416

Integer Overflow or Wraparound

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References