Application crash via embedded-NUL pathname length mismatch
Published Jan 3, 2020 · Updated Aug 5, 2024
NULL-pointer dereference in SQLite 3.30.1 allows attackers to crash applications via crafted SQL against the Zipfile extension. In zipfileStep, the code increments the original byte length after sqlite3_mprintf truncates an embedded-NUL pathname, leaving the recorded length larger than the allocated string. The crash requires arbitrary SQL execution and the optional Zipfile extension, which default builds do not deploy.
Summary
What happened
NULL-pointer dereference in SQLite 3.30.1 allows attackers to crash applications via crafted SQL against the Zipfile extension. In zipfileStep, the code increments the original byte length after sqlite3_mprintf truncates an embedded-NUL pathname, leaving the recorded length larger than the allocated string. The crash requires arbitrary SQL execution and the optional Zipfile extension, which default builds do not deploy.
The record
- CVE
- CVE-2019-19959
- Published
- Jan 3, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- SQLite Zipfile embedded-NUL regression testproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo