Remote code execution via predictable temporary filename
Published May 23, 2023 · Updated Mar 5, 2025
Insecure temporary-file handling in Xerial SQLite JDBC 3.6.14.1 through 3.41.2.1 allows remote authenticated users to execute code. SQLiteConnection.extractResource derives an external database filename in java.io.tmpdir from the JDBC resource URL's hashCode instead of creating a unique path. Exploitation requires an application to accept an attacker-controlled JDBC URL and reach external-resource extraction, placing execution in the Java process context.
Summary
What happened
Insecure temporary-file handling in Xerial SQLite JDBC 3.6.14.1 through 3.41.2.1 allows remote authenticated users to execute code. SQLiteConnection.extractResource derives an external database filename in java.io.tmpdir from the JDBC resource URL's hashCode instead of creating a unique path. Exploitation requires an application to accept an attacker-controlled JDBC URL and reach external-resource extraction, placing execution in the Java process context.
The record
- CVE
- CVE-2023-32697
- Published
- May 23, 2023
- Updated
- Mar 5, 2025
- Vendor
- Xerial
- Product
- SQLite JDBC
- Classifications
- CWE-94
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 23, 2023CVE publishedPublication date reported by the CVE source.
- Mar 5, 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.6.14.1, < 3.41.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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