LiveActive security incident?Get immediate response
CVE Record

CVE-2024-8443: Libopensc: heap buffer overflow in openpgp driver when generating key

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.

LowCVSS 2.9Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2024-8443 affects OpenSC smart-card tooling. A malicious USB device or smart card could trigger a memory corruption bug while a user enrolls a card with pkcs15-init. The scenario is narrow because it needs physical access, user interaction, and a specific enrollment workflow, but successful exploitation could potentially run code.

Executive priority

Treat this as a targeted workstation and enrollment-system risk, not a broad internet-facing emergency. Prioritize organizations that issue smart cards, manage OpenPGP tokens, or handle untrusted hardware. Patch through vendor channels once fixes are available.

Technical view

The issue is a heap-based buffer overflow in the libopensc OpenPGP driver during key generation/enrollment. Malicious APDU responses from a crafted device or card can cause out-of-bounds memory behavior. Red Hat lists opensc as affected on RHEL 7, 8, 9, and 10. CVSS 3.1 is 2.9: physical, high complexity, user interaction required.

Likely exposure

Exposure is most likely on Linux systems with OpenSC installed and used for OpenPGP smart-card enrollment, especially where pkcs15-init is used with untrusted or newly issued devices. General servers without smart-card enrollment workflows are less likely to be exposed.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Abuse requires a malicious physical USB device or smart card and a user performing enrollment. The potential impact is serious locally, but operational likelihood appears limited by physical access and workflow requirements.

Researcher notes

Evidence supports memory corruption and possible arbitrary code execution, but exploitability is constrained by physical access, high complexity, and user interaction. The source bundle does not provide exploit details, proof of active exploitation, or complete fixed-version mapping across all distributions.

Mitigation direction

  • Check Red Hat and Debian guidance for fixed OpenSC packages.
  • Update opensc/libopensc through supported distribution channels when available.
  • Restrict pkcs15-init enrollment to trusted smart cards and USB readers.
  • Avoid enrolling unknown, found, or externally supplied smart-card devices.
  • Prioritize endpoints and admin workstations that perform card issuance or enrollment.

Validation and detection

  • Inventory systems with opensc or libopensc installed.
  • Identify hosts where pkcs15-init or OpenPGP smart-card enrollment is used.
  • Confirm affected RHEL 7, 8, 9, and 10 systems against vendor advisories.
  • Review device-handling procedures for untrusted smart cards or USB readers.
  • Track Red Hat Bugzilla and Debian LTS advisory status for remediation details.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-8443 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.9CVSS 3.1LowCVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N0.42.5redhat

Vulnerability scoring details

Base CVSS 3.1 score

2.9Low
CVSS 3.1 vector shape for CVE-2024-8443Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Made public.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineredhat

    Reported to Red Hat.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendoropenscopensc, 0.26.0unaffected
Red HatRed Hat Enterprise Linux 10openscaffected
Red HatRed Hat Enterprise Linux 7openscaffected
Red HatRed Hat Enterprise Linux 8openscaffected
Red HatRed Hat Enterprise Linux 9openscaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.