Data exposure and corruption via unchecked APDU lengths
Published Sep 3, 2024 · Updated Jun 30, 2026
Use of uninitialized memory in OpenSC before 0.26.0 allows physically proximate attackers to disclose or alter data or interrupt service. Multiple libopensc card-driver paths trust response lengths or status bytes and then read uninitialized portions of APDU buffers. A crafted USB device or smart card must supply malformed APDU responses; the reported effects are limited to low-impact disclosure, alteration, or interruption.
Summary
What happened
Use of uninitialized memory in OpenSC before 0.26.0 allows physically proximate attackers to disclose or alter data or interrupt service. Multiple libopensc card-driver paths trust response lengths or status bytes and then read uninitialized portions of APDU buffers. A crafted USB device or smart card must supply malformed APDU responses; the reported effects are limited to low-impact disclosure, alteration, or interruption.
The record
- CVE
- CVE-2024-45616
- Published
- Sep 3, 2024
- Updated
- Jun 30, 2026
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-457, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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