{"id":"CVE-2021-45346","details":"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.","aliases":["BIT-sqlite-2021-45346"],"modified":"2026-08-18T14:04:57.010938Z","published":"2022-02-14T19:15:07.793Z","references":[{"type":"ADVISORY","url":"https://security.netapp.com/advisory/ntap-20220303-0001/"},{"type":"ADVISORY","url":"https://sqlite.org/forum/forumpost/056d557c2f8c452ed5"},{"type":"ADVISORY","url":"https://sqlite.org/forum/forumpost/53de8864ba114bf6"},{"type":"ADVISORY","url":"https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves"},{"type":"EVIDENCE","url":"https://github.com/guyinatuxedo/sqlite3_record_leaking"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/sqlite/sqlite","events":[{"introduced":"a7eaa518f83d1ff4660b720038ccba45c1f4c758"},{"last_affected":"315e3122c37b2dbe0fb7b3a4c3b9b6961e3bda96"}],"database_specific":{"source":"CPE_STRING","cpe":["cpe:2.3:a:sqlite:sqlite:3.35.1:*:*:*:*:*:*:*","cpe:2.3:a:sqlite:sqlite:3.37.0:*:*:*:*:*:*:*"],"extracted_events":[{"introduced":"3.35.1"},{"last_affected":"3.35.1"},{"introduced":"3.37.0"},{"last_affected":"3.37.0"}]}}],"versions":["3.35.1","3.37.0","version-3.37.0","version-3.36.0","same-as-3.35.3","version-3.35.2","version-3.35.1"],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2021-45346.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"}]}