CVE-2024-8443: Libopensc: heap buffer overflow in openpgp driver when generating key
Noroxi assessment
Priority: Monitor (action score 11/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: github.com/OpenSC/OpenSC opensc 0.26.0.
Low priority for now. Upgrade to github.com/OpenSC/OpenSC opensc 0.26.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A heap-based buffer overflow vulnerability was found in the libopensc OpenPGP driver. A crafted USB device or smart card with malicious responses to the APDUs during the card enrollment process using the `pkcs15-init` tool may lead to out-of-bound rights, possibly resulting in arbitrary code execution.
- Published
- Sep 10, 2024
- Updated
- Jun 30, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- CWE-122
Report tools
Action score
11
Monitor
Low priority for now.
- CVSS
- 11 / 40 · 2.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 2.9
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| opensc project | opensc | cpe:2.3:a:opensc_project:opensc |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensc project openscall versions
- redhat enterprise linux7.0
- redhat enterprise linux8.0
- redhat enterprise linux9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
github.com/OpenSC/OpenSC opensc
- 0.26.0 and later · before 0.26.0affected · semver
Red Hat Red Hat Enterprise Linux 10
- all versionsaffected
Red Hat Red Hat Enterprise Linux 7
- all versionsaffected
Red Hat Red Hat Enterprise Linux 8
- all versionsaffected
Red Hat Red Hat Enterprise Linux 9
- all versionsaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | opensc | before 0.26.0-r0 | 0.26.0-r0 |
| Debian:11 | opensc | before 0.21.0-1+deb11u1 | 0.21.0-1+deb11u1 |
| Debian:12 | opensc | before 0.23.0-0.3+deb12u2 | 0.23.0-0.3+deb12u2 |
| Debian:13 | opensc | before 0.25.1-2.1 | 0.25.1-2.1 |
| openSUSE:Leap 15.6 | opensc | before 0.22.0-150600.11.3.1 | 0.22.0-150600.11.3.1 |
| openSUSE:Leap Micro 5.5 | opensc | before 0.22.0-150400.3.12.1 | 0.22.0-150400.3.12.1 |
| openSUSE:Tumbleweed | opensc | before 0.25.1-2.1 | 0.25.1-2.1 |
| SUSE:Linux Enterprise Micro 5.1 | opensc | before 0.19.0-150100.3.31.1 | 0.19.0-150100.3.31.1 |
| SUSE:Linux Enterprise Micro 5.3 | opensc | before 0.22.0-150400.3.12.1 | 0.22.0-150400.3.12.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | opensc | before 0.22.0-150600.11.3.1 | 0.22.0-150600.11.3.1 |
| SUSE:Linux Enterprise Server 12 SP5 | opensc | before 0.13.0-3.31.1 | 0.13.0-3.31.1 |
| SUSE:Linux Micro 6.0 | opensc | before 0.24.0-3.1 | 0.24.0-3.1 |
| SUSE:Linux Micro 6.1 | opensc | before 0.24.0-slfo.1.1_2.1 | 0.24.0-slfo.1.1_2.1 |
Same product
opensc project: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-6502sc_context_create in ctx.c in libopensc in OpenSC 0.19.0 has a memory leak, as demonstrated by a call from eidenv.31Monitor
- CVE-2021-34193Stack overflow vulnerability in OpenSC smart card middleware before 0.23 via crafted responses to APDUs.30Monitor
- CVE-2019-16058An issue was discovered in the pam_p11 component 0.2.0 and 0.3.0 for OpenSC.30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-5992Jan 31, 2024 · Opensc: side-channel leaks while stripping encryption pkcs#1 padding23Monitor
- ← EarlierCVE-2024-1454Feb 12, 2024 · Opensc: memory use after free in authentic driver when updating token info13Monitor
- Later →CVE-2025-49010Mar 30, 2026 · OpenSC: Stack-buffer-overflow WRITE in GET RESPONSE27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| github.com/OpenSC/OpenSC opensc | 0.26.0 | Vendor (CNA) |
| alpine:opensc | 0.26.0-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:opensc | 0.23.0-0.3+deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:opensc | 0.22.0-150600.11.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:opensc | 0.13.0-3.31.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:opensc | 0.22.0-150600.11.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS vector
CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.