Program crash via unchecked Oberthur metadata lengths
Published Apr 18, 2022 · Updated Nov 3, 2025
Heap buffer overflow in OpenSC before 0.22.0 allows attackers to crash programs using the library via malformed Oberthur card data. The PKCS#15 Oberthur initialization code trusts length-prefixed label, identifier, subject, and OID fields before reading or copying beyond the metadata buffer. Triggering the flaw requires OpenSC to initialize and parse a crafted Oberthur-compatible card image; the bounded consequence is a host-process crash.
Summary
What happened
Heap buffer overflow in OpenSC before 0.22.0 allows attackers to crash programs using the library via malformed Oberthur card data. The PKCS#15 Oberthur initialization code trusts length-prefixed label, identifier, subject, and OID fields before reading or copying beyond the metadata buffer. Triggering the flaw requires OpenSC to initialize and parse a crafted Oberthur-compatible card image; the bounded consequence is a host-process crash.
The record
- CVE
- CVE-2021-42781
- Published
- Apr 18, 2022
- Updated
- Nov 3, 2025
- Vendor
- OpenSC Project
- Product
- OpenSC
- Classifications
- CWE-119, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 18, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=opensc 0.22.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.
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