{ "CVE_data_meta": { "ASSIGNER": "cve@mitre.org", "ID": "CVE-2021-45346", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "n/a", "version": { "version_data": [ { "version_value": "n/a" } ] } } ] }, "vendor_name": "n/a" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "** DISPUTED ** 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." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "n/a" } ] } ] }, "references": { "reference_data": [ { "url": "https://github.com/guyinatuxedo/sqlite3_record_leaking", "refsource": "MISC", "name": "https://github.com/guyinatuxedo/sqlite3_record_leaking" }, { "refsource": "CONFIRM", "name": "https://security.netapp.com/advisory/ntap-20220303-0001/", "url": "https://security.netapp.com/advisory/ntap-20220303-0001/" }, { "refsource": "MISC", "name": "https://sqlite.org/forum/forumpost/53de8864ba114bf6", "url": "https://sqlite.org/forum/forumpost/53de8864ba114bf6" }, { "refsource": "MISC", "name": "https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves", "url": "https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves" }, { "refsource": "MISC", "name": "https://sqlite.org/forum/forumpost/056d557c2f8c452ed5", "url": "https://sqlite.org/forum/forumpost/056d557c2f8c452ed5" } ] } }