Application crash via unchecked changeset value read
Published Dec 25, 2023 · Updated Dec 18, 2025
Heap-based buffer over-read in SQLite 3.43.0 and earlier allows attackers to crash session-enabled applications via a corrupted changeset. sessionReadRecord passes an unchecked pointer near the end of SessionInput to sessionGetI64, which reads eight bytes for integer or float values. Reachability requires SQLite compiled with SQLITE_ENABLE_SESSION and an application that uses the Session C APIs to process an adversarially corrupted changeset; the demonstrated consequence is process termination.
Summary
What happened
Heap-based buffer over-read in SQLite 3.43.0 and earlier allows attackers to crash session-enabled applications via a corrupted changeset. sessionReadRecord passes an unchecked pointer near the end of SessionInput to sessionGetI64, which reads eight bytes for integer or float values. Reachability requires SQLite compiled with SQLITE_ENABLE_SESSION and an application that uses the Session C APIs to process an adversarially corrupted changeset; the demonstrated consequence is process termination.
The record
- CVE
- CVE-2023-7104
- Published
- Dec 25, 2023
- Updated
- Dec 18, 2025
- Vendor
- SQLite
- Product
- SQLite
- Classifications
- CWE-119, CWE-122
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 25, 2023CVE publishedPublication date reported by the CVE source.
- Dec 18, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0
- Affected versionversion=3.1
- Affected versionversion=3.10
- Affected versionversion=3.11
- Affected versionversion=3.12
- Affected versionversion=3.13
- Affected versionversion=3.14
- Affected versionversion=3.15
- Affected versionversion=3.16
- Affected versionversion=3.17
- Affected versionversion=3.18
- Affected versionversion=3.19
- Affected versionversion=3.2
- Affected versionversion=3.20
- Affected versionversion=3.21
- Affected versionversion=3.22
- Affected versionversion=3.23
- Affected versionversion=3.24
- Affected versionversion=3.25
- Affected versionversion=3.26
- Affected versionversion=3.27
- Affected versionversion=3.28
- Affected versionversion=3.29
- Affected versionversion=3.3
- Affected versionversion=3.30
- Affected versionversion=3.31
- Affected versionversion=3.32
- Affected versionversion=3.33
- Affected versionversion=3.34
- Affected versionversion=3.35
- Affected versionversion=3.36
- Affected versionversion=3.37
- Affected versionversion=3.38
- Affected versionversion=3.39
- Affected versionversion=3.4
- Affected versionversion=3.40
- Affected versionversion=3.41
- Affected versionversion=3.42
- Affected versionversion=3.43
- Affected versionversion=3.5
- Affected versionversion=3.6
- Affected versionversion=3.7
- Affected versionversion=3.8
- Affected versionversion=3.9
What conditions does exploitation require?
What is affected?
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
- sessionfuzz malformed changeset reproducerproof 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