CVE Vulnerabilities

CVE-2019-8457

Out-of-bounds Read

Published: May 30, 2019 | Modified: Nov 07, 2023
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Sqlite Sqlite 3.6.0 (including) 3.27.2 (including)
Red Hat Enterprise Linux 8 RedHat sqlite-0:3.26.0-6.el8 *
Red Hat Enterprise Linux 8 RedHat sqlite-0:3.26.0-6.el8 *
Chromium Ubuntu trusty *
Db5.3 Ubuntu bionic *
Db5.3 Ubuntu cosmic *
Db5.3 Ubuntu devel *
Db5.3 Ubuntu disco *
Db5.3 Ubuntu eoan *
Db5.3 Ubuntu focal *
Db5.3 Ubuntu groovy *
Db5.3 Ubuntu hirsute *
Db5.3 Ubuntu impish *
Db5.3 Ubuntu jammy *
Db5.3 Ubuntu kinetic *
Db5.3 Ubuntu lunar *
Db5.3 Ubuntu mantic *
Db5.3 Ubuntu noble *
Db5.3 Ubuntu oracular *
Db5.3 Ubuntu trusty *
Db5.3 Ubuntu trusty/esm *
Db5.3 Ubuntu xenial *
Qtwebengine-opensource-src Ubuntu bionic *
Qtwebengine-opensource-src Ubuntu cosmic *
Qtwebengine-opensource-src Ubuntu disco *
Qtwebengine-opensource-src Ubuntu eoan *
Qtwebengine-opensource-src Ubuntu groovy *
Qtwebengine-opensource-src Ubuntu hirsute *
Qtwebengine-opensource-src Ubuntu impish *
Qtwebengine-opensource-src Ubuntu kinetic *
Qtwebengine-opensource-src Ubuntu lunar *
Qtwebengine-opensource-src Ubuntu mantic *
Qtwebengine-opensource-src Ubuntu trusty *
Sqlcipher Ubuntu bionic *
Sqlcipher Ubuntu cosmic *
Sqlcipher Ubuntu devel *
Sqlcipher Ubuntu disco *
Sqlcipher Ubuntu eoan *
Sqlcipher Ubuntu esm-apps/bionic *
Sqlcipher Ubuntu esm-apps/focal *
Sqlcipher Ubuntu esm-apps/jammy *
Sqlcipher Ubuntu esm-apps/noble *
Sqlcipher Ubuntu esm-apps/xenial *
Sqlcipher Ubuntu focal *
Sqlcipher Ubuntu groovy *
Sqlcipher Ubuntu hirsute *
Sqlcipher Ubuntu impish *
Sqlcipher Ubuntu jammy *
Sqlcipher Ubuntu kinetic *
Sqlcipher Ubuntu lunar *
Sqlcipher Ubuntu mantic *
Sqlcipher Ubuntu noble *
Sqlcipher Ubuntu oracular *
Sqlcipher Ubuntu trusty *
Sqlcipher Ubuntu xenial *
Sqlite3 Ubuntu bionic *
Sqlite3 Ubuntu cosmic *
Sqlite3 Ubuntu devel *
Sqlite3 Ubuntu disco *
Sqlite3 Ubuntu eoan *
Sqlite3 Ubuntu focal *
Sqlite3 Ubuntu groovy *
Sqlite3 Ubuntu hirsute *
Sqlite3 Ubuntu impish *
Sqlite3 Ubuntu jammy *
Sqlite3 Ubuntu kinetic *
Sqlite3 Ubuntu lunar *
Sqlite3 Ubuntu mantic *
Sqlite3 Ubuntu noble *
Sqlite3 Ubuntu oracular *
Sqlite3 Ubuntu trusty *
Sqlite3 Ubuntu trusty/esm *
Sqlite3 Ubuntu xenial *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References