CVE Vulnerabilities

CVE-2020-13630

Use After Free

Published: May 27, 2020 | Modified: Nov 07, 2023
CVSS 3.x
7
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
4.4 MEDIUM
AV:L/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
7 MODERATE
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.

Weakness

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

Affected Software

Name Vendor Start Version End Version
Sqlite Sqlite * 3.32.0 (excluding)
Red Hat Enterprise Linux 8 RedHat sqlite-0:3.26.0-11.el8 *
Red Hat Enterprise Linux 8 RedHat mingw-binutils-0:2.30-3.el8 *
Red Hat Enterprise Linux 8 RedHat mingw-bzip2-0:1.0.6-14.el8 *
Red Hat Enterprise Linux 8 RedHat mingw-filesystem-0:104-2.el8 *
Red Hat Enterprise Linux 8 RedHat mingw-sqlite-0:3.26.0.0-1.el8 *
Red Hat Enterprise Linux 8 RedHat sqlite-0:3.26.0-11.el8 *
Sqlite3 Ubuntu bionic *
Sqlite3 Ubuntu devel *
Sqlite3 Ubuntu eoan *
Sqlite3 Ubuntu focal *
Sqlite3 Ubuntu trusty *
Sqlite3 Ubuntu upstream *
Sqlite3 Ubuntu xenial *

Extended Description

The use of previously-freed memory can have any number of adverse consequences, ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw. The simplest way data corruption may occur involves the system’s reuse of the freed memory. Use-after-free errors have two common and sometimes overlapping causes:

In this scenario, the memory in question is allocated to another pointer validly at some point after it has been freed. The original pointer to the freed memory is used again and points to somewhere within the new allocation. As the data is changed, it corrupts the validly used memory; this induces undefined behavior in the process. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Potential Mitigations

References