CVE-2021-45346: Sqlite vulnerability
Affected: Sqlite · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 76% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
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.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Sqlite
- Published
- February 2022
CoverageNo articles yet
No CyberSIXT article names CVE-2021-45346 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-401cwe.mitre.org
- github.com/guyinatuxedo/sqlite3_record_leakinggithub.com
- security.netapp.com/advisory/ntap-20220303-0001security.netapp.com
- sqlite.org/forum/forumpost/53de8864ba114bf6sqlite.org
- sqlite.org/cves.html#status_of_recent_sqlite_cvessqlite.org
- sqlite.org/forum/forumpost/056d557c2f8c452ed5sqlite.org