MITRE disputed

** 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 pa

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 data

NIST AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

NIST AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

https://sqlite.org/forum/forumpost/056d557c2f8c452ed5 No Types Assigned

https://sqlite.org/forum/forumpost/056d557c2f8c452ed5 Vendor Advisory

https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves No Types Assigned

https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves Vendor Advisory

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..

** 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 pa

https://sqlite.org/forum/forumpost/056d557c2f8c452ed5 [No Types Assigned]

https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves [No Types Assigned]

OR
     *cpe:2.3:a:netapp:ontap_select_deploy_administration_utility:-:*:*:*:*:*:*:*

https://security.netapp.com/advisory/ntap-20220303-0001/ No Types Assigned

https://security.netapp.com/advisory/ntap-20220303-0001/ Third Party Advisory

https://sqlite.org/forum/forumpost/53de8864ba114bf6 No Types Assigned

https://sqlite.org/forum/forumpost/53de8864ba114bf6 Vendor Advisory

https://sqlite.org/forum/forumpost/53de8864ba114bf6 [No Types Assigned]

https://security.netapp.com/advisory/ntap-20220303-0001/ [No Types Assigned]

OR
     *cpe:2.3:a:sqlite:sqlite:3.35.1:*:*:*:*:*:*:*
     *cpe:2.3:a:sqlite:sqlite:3.37.0:*:*:*:*:*:*:*

NIST (AV:N/AC:L/Au:S/C:P/I:N/A:N)

NIST AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

NIST CWE-401

https://github.com/guyinatuxedo/sqlite3_record_leaking No Types Assigned

https://github.com/guyinatuxedo/sqlite3_record_leaking Exploit, Third Party Advisory