Code execution via unchecked OpenPGP response handling
Published Sep 10, 2024 · Updated Jun 30, 2026
Heap buffer overflow in OpenSC before 0.26.0 allows physically proximate attackers to execute code through crafted smart-card responses. The OpenPGP key parser accepts response tags for a different key algorithm and accesses invalid union members, while the fingerprint writer fails to verify that the selected key slot fits its heap buffer. Exploitation requires a crafted USB token or smart card and user interaction during RSA or ECDSA key generation or card enrollment.
Summary
What happened
Heap buffer overflow in OpenSC before 0.26.0 allows physically proximate attackers to execute code through crafted smart-card responses. The OpenPGP key parser accepts response tags for a different key algorithm and accesses invalid union members, while the fingerprint writer fails to verify that the selected key slot fits its heap buffer. Exploitation requires a crafted USB token or smart card and user interaction during RSA or ECDSA key generation or card enrollment.
The record
- CVE
- CVE-2024-8443
- Published
- Sep 10, 2024
- Updated
- Jun 30, 2026
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-787, CWE-122, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 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?
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