Memory corruption via invalidated SQLite column-name pointers
Published Mar 12, 2021 · Updated Aug 3, 2024
Use-after-free in Diesel before 1.4.6 allows attackers to corrupt memory when applications execute named SQLite queries. SqliteConnection::query_by_name stores sqlite3_column_name pointers as string slices, then sqlite3_step invalidates those pointers before later use. An application must use the SQLite backend and named-query infrastructure; dereferencing the invalid slices can crash the process or corrupt its memory.
Summary
What happened
Use-after-free in Diesel before 1.4.6 allows attackers to corrupt memory when applications execute named SQLite queries. SqliteConnection::query_by_name stores sqlite3_column_name pointers as string slices, then sqlite3_step invalidates those pointers before later use. An application must use the SQLite backend and named-query infrastructure; dereferencing the invalid slices can crash the process or corrupt its memory.
The record
- CVE
- CVE-2021-28305
- Published
- Mar 12, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 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?
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
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