{"id":"CVE-2021-45346","aliases":["BIT-sqlite-2021-45346","DEBIAN-CVE-2021-45346","EUVD-2021-32119","GHSA-w3q4-xr8h-32gf","UBUNTU-CVE-2021-45346"],"status":"disputed","title":"A Memory Leak vulnerabilty exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously...","description":"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.","severity":{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-08","score":0.01628,"percentile":0.76337,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-401"],"published":"2022-02-14T00:00:00Z","modified":"2026-10-24T10:30:15Z","fixes":[{"ecosystem":"Bitnami","package":"sqlite","fixed_in":["3.35.2","3.37.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"sqlite","ranges":[{"type":"SEMVER","events":[{"introduced":"3.35.1"},{"fixed":"3.35.2"},{"introduced":"3.37.0"},{"fixed":"3.37.1"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.40.1-2","3.40.1-2+deb12u1","3.40.1-2+deb12u2","3.42.0-1","3.43.0-1","3.43.1-1","3.43.2-1","3.44.0-1","3.44.2-1","3.45.0-1","3.45.1-1","3.45.2-1","3.45.3-1","3.45.3-2~exp1","3.46.0-1","3.46.1-1","3.46.1-2","3.46.1-2~exp","3.46.1-3","3.46.1-4","3.46.1-5","3.46.1-6","3.46.1-7","3.46.1-8","3.46.1-9","3.53.2-1","3.53.3-1","3.53.4-1","3.53.4-2"]},{"source":"osv","ecosystem":"Debian:13","package":"sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.46.1-7","3.46.1-7+deb13u1","3.46.1-7+deb13u2","3.46.1-8","3.46.1-9","3.53.2-1","3.53.3-1","3.53.4-1","3.53.4-2"]},{"source":"osv","ecosystem":"Debian:14","package":"sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.46.1-7","3.46.1-8","3.46.1-9","3.53.2-1","3.53.3-1","3.53.4-1","3.53.4-2"]}],"products":[{"vendor":"netapp","product":"ontap_select_deploy_administration_utility"},{"vendor":"sqlite","product":"sqlite"}],"references":[{"url":"https://github.com/guyinatuxedo/sqlite3_record_leaking","tags":["x_transferred","Exploit","Third Party Advisory","advisory","evidence","report"]},{"url":"https://security.netapp.com/advisory/ntap-20220303-0001/","tags":["x_transferred","Third Party Advisory","advisory"]},{"url":"https://sqlite.org/forum/forumpost/53de8864ba114bf6","tags":["x_transferred","Vendor Advisory","advisory","report"]},{"url":"https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves","tags":["x_transferred","Vendor Advisory","advisory"]},{"url":"https://sqlite.org/forum/forumpost/056d557c2f8c452ed5","tags":["x_transferred","Vendor Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-45346","tags":["web"]},{"url":"https://security.netapp.com/advisory/ntap-20220303-0001"},{"url":"https://github.com/advisories/GHSA-w3q4-xr8h-32gf"},{"url":"https://security-tracker.debian.org/tracker/CVE-2021-45346","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2021-45346","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-45346","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2021-45346","description":"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.","status":"disputed","published":"2022-02-14T00:00:00Z","modified":"2024-08-04T04:39:20.536Z","updated_at":"2026-11-02T14:33:02.930115Z"}],"euvd":[{"id":"EUVD-2021-32119","description":"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.","status":"published","published":"2022-02-14T00:00:00Z","modified":"2024-08-04T04:39:20Z","updated_at":"2026-11-03T03:08:27.448176Z"}],"ghsa":[{"id":"GHSA-w3q4-xr8h-32gf","title":"A Memory Leak vulnerabilty exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously...","description":"A Memory Leak vulnerabilty 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 malicous user obtain sensitive information..","status":"published","published":"2022-02-15T00:02:45Z","modified":"2024-03-30T05:01:32Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-401"],"updated_at":"2026-11-02T14:55:44.111751Z"}],"nvd":[{"id":"CVE-2021-45346","description":"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.","status":"disputed","published":"2022-02-14T19:15:07.793Z","modified":"2026-06-17T04:13:18.233Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"primary"},{"version":"2.0","score":4,"vector":"AV:N/AC:L/Au:S/C:P/I:N/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-401"],"updated_at":"2026-11-02T14:07:04.6896Z"}],"osv":[{"id":"CVE-2021-45346","description":"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.","status":"published","published":"2022-02-14T19:15:07.793Z","modified":"2026-10-24T10:30:15.180325668Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:44:22.18434Z"},{"id":"DEBIAN-CVE-2021-45346","description":"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.","status":"published","published":"2022-02-14T19:15:07.793Z","modified":"2026-10-23T18:04:50.797736656Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:35.799676Z"},{"id":"UBUNTU-CVE-2021-45346","description":"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.","status":"withdrawn","published":"2022-02-14T19:15:00Z","modified":"2026-07-21T18:18:27.059122177Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:54:30.277322Z"},{"id":"BIT-sqlite-2021-45346","description":"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.","status":"published","published":"2024-03-06T11:06:14.888Z","modified":"2026-09-08T08:48:19.525362837Z","updated_at":"2026-11-02T15:28:35.111822Z"}]}}