Skip to content
Fencer Vulns
medium 4.3

CVE-2021-45346 json

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Da…

published 2022-02-14 4 y ago modified 2026-09-08 2 mo ago also BIT-sqlite-2021-45346 , EUVD-2021-32119

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 76%
public exploits
0
none known

Summary

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

Patch / fix

  • bitnami sqlite 3.35.2, 3.37.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-45346 updated cvss 4.3

sqlite: crafted SQL query allows a malicious user to obtain sensitive information

  • Red Hat Enterprise Linux 6 lemon, sqlite, sqlite-tcl Red Hat Enterprise Linux 7 lemon, sqlite, sqlite-tcl
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 mingw-sqlite, mingw32-sqlite, mingw64-sqlite
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 8 lemon, sqlite, sqlite-libs Red Hat Enterprise Linux 9 sqlite, sqlite-libs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.63% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/guyinatuxedo/sqlite3_record_leaking referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
OSV 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami sqlite
>=3.35.1, <3.35.2
>=3.37.0, <3.37.1
3.35.2
3.37.1

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.