Physical double free via duplicate object insertion
Published Apr 29, 2020 · Updated Aug 5, 2024
Double-free in OpenSC before 0.20.0 allows attackers to trigger memory corruption via crafted CoolKey object processing. The coolkey_add_object function appends objects without a uniqueness check, so duplicate entries are later released twice by coolkey_free_private_data. Physically proximate attackers can reach the smart-card handling path; the flaw can corrupt memory in the consuming process.
Summary
What happened
Double-free in OpenSC before 0.20.0 allows attackers to trigger memory corruption via crafted CoolKey object processing. The coolkey_add_object function appends objects without a uniqueness check, so duplicate entries are later released twice by coolkey_free_private_data. Physically proximate attackers can reach the smart-card handling path; the flaw can corrupt memory in the consuming process.
The record
- CVE
- CVE-2019-20792
- Published
- Apr 29, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
No sourced classifications are available.
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