Read-after-free via premature HAVING rewrite
Published Mar 23, 2021 · Updated Aug 3, 2024
Use-after-free in SQLite before 3.34.1 allows local users who can run crafted SQL to trigger an internal read from freed memory. In havingToWhereExprCb() in src/select.c, a correlated WHERE term can be moved before a constant-false HAVING term during aggregate-subquery rewriting, leaving aggregate processing to read released memory. Arbitrary SQL execution is required; SQLite reports that no crash or code execution has been demonstrated and the condition is visible only under a memory sanitizer.
Summary
What happened
Use-after-free in SQLite before 3.34.1 allows local users who can run crafted SQL to trigger an internal read from freed memory. In havingToWhereExprCb() in src/select.c, a correlated WHERE term can be moved before a constant-false HAVING term during aggregate-subquery rewriting, leaving aggregate processing to read released memory. Arbitrary SQL execution is required; SQLite reports that no crash or code execution has been demonstrated and the condition is visible only under a memory sanitizer.
The record
- CVE
- CVE-2021-20227
- Published
- Mar 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- SQLite
- Product
- SQLite
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=sqlite 3.34.1
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
- SQLite having.test regression caseproof 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