Memory corruption via double-free key import
Published Jul 13, 2021 · Updated Aug 3, 2024
Double-free memory corruption in Qualcomm Snapdragon platforms allows local users to corrupt memory during key parsing and import. The closed-source trusted application frees the same heap allocation twice while parsing or importing key material, corrupting its allocator state. Public records establish a local, interaction-free path but do not disclose the malformed key format or a specific post-corruption effect.
Summary
What happened
Double-free memory corruption in Qualcomm Snapdragon platforms allows local users to corrupt memory during key parsing and import. The closed-source trusted application frees the same heap allocation twice while parsing or importing key material, corrupting its allocator state. Public records establish a local, interaction-free path but do not disclose the malformed key format or a specific post-corruption effect.
The record
- CVE
- CVE-2021-1888
- Published
- Jul 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 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.
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