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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2021-45346US | medium4.3 | — | ||
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 r… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/guyinatuxedo/sqlite3_record_leakingADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2021-45346WEB
- https://security.netapp.com/advisory/ntap-20220303-0001/ADVISORY
- https://sqlite.org/forum/forumpost/056d557c2f8c452ed5ADVISORY
- https://sqlite.org/forum/forumpost/53de8864ba114bf6ADVISORY
- https://www.sqlite.org/cves.html#status_of_recent_sqlite_cvesADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan