4
CVSSv2

CVE-2021-45346

Published: 14/02/2022 Updated: 11/04/2024
CVSS v2 Base Score: 4 | Impact Score: 2.9 | Exploitability Score: 8
CVSS v3 Base Score: 4.3 | Impact Score: 1.4 | Exploitability Score: 2.8
VMScore: 356
Vector: AV:N/AC:L/Au:S/C:P/I:N/A:N

Vulnerability 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.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

sqlite sqlite 3.35.1

sqlite sqlite 3.37.0

netapp ontap select deploy administration utility -

Vendor Advisories

Debian Bug report logs - #1005974 sqlite3: CVE-2021-45346 memory leak vulnerability in SQLite Package: src:sqlite3; Maintainer for src:sqlite3 is Laszlo Boszormenyi (GCS) <gcs@debianorg>; Reported by: Neil Williams <codehelp@debianorg> Date: Fri, 18 Feb 2022 14:18:01 UTC Severity: important Tags: security, upstream ...

Github Repositories

Beyond_Oblivion So many database implementations will have the option to save the data in the database to a file, which will then be loaded when the database process restarts This is so the data will persist when the database process stops Now in many database implementations, if you can write to this file, you can cause certain database operations like queries, to do other t