Card-management corruption via freed file object
Published Feb 12, 2024 · Updated Nov 7, 2025
Use-after-free in the AuthentIC driver in OpenSC 0.25.0 allows physically proximate attackers to corrupt card-management operations. In authentic_emu_update_tokeninfo, a successful sc_get_challenge call wrongly frees the selected file object, which subsequent code continues to use. Exploitation requires user interaction during pkcs15-init enrollment and a crafted USB device or smart card that returns malicious APDU responses.
Summary
What happened
Use-after-free in the AuthentIC driver in OpenSC 0.25.0 allows physically proximate attackers to corrupt card-management operations. In authentic_emu_update_tokeninfo, a successful sc_get_challenge call wrongly frees the selected file object, which subsequent code continues to use. Exploitation requires user interaction during pkcs15-init enrollment and a crafted USB device or smart card that returns malicious APDU responses.
The record
- CVE
- CVE-2024-1454
- Published
- Feb 12, 2024
- Updated
- Nov 7, 2025
- Vendor
- OpenSC Project
- Product
- OpenSC
- Classifications
- CWE-416, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 7, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.25.0
What conditions does exploitation require?
What is affected?
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.
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