Application crashes via five memory-safety flaws
Published Aug 22, 2023 · Updated Nov 3, 2025
Memory-safety flaws in OpenSC before 0.22.0 allow attackers controlling smart-card responses to crash applications using the middleware. The duplicate identifier spans a double free in sc_pkcs15_free_tokeninfo, a use-after-free in sc_file_valid, a use-after-return in insert_pin, and heap and stack buffer overflows. A malicious or malfunctioning smart card must return crafted APDU data; the bounded reported consequence is process termination.
Summary
What happened
Memory-safety flaws in OpenSC before 0.22.0 allow attackers controlling smart-card responses to crash applications using the middleware. The duplicate identifier spans a double free in sc_pkcs15_free_tokeninfo, a use-after-free in sc_file_valid, a use-after-return in insert_pin, and heap and stack buffer overflows. A malicious or malfunctioning smart card must return crafted APDU data; the bounded reported consequence is process termination.
The record
- CVE
- CVE-2021-34193
- Published
- Aug 22, 2023
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 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?
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.
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