LiveActive security incident?Get immediate response
CVE Record

CVE-2021-42778: A heap double free issue was found in Opensc before version 0.22.0 in sc_pkcs15_free_tokeninfo.

A heap double free issue was found in Opensc before version 0.22.0 in sc_pkcs15_free_tokeninfo.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-42778 is a heap double-free flaw in OpenSC, reported before version 0.22.0. OpenSC is smart-card middleware, so exposure is most relevant where systems use OpenSC for tokens, smart cards, or PKCS#15 workflows. Public sources do not provide a CVSS score or confirm active exploitation.

Executive priority

Handle through normal vulnerability management unless OpenSC supports critical authentication workflows. There is no cited active exploitation or CVSS score, but memory-safety bugs in authentication-related middleware justify timely inventory and vendor-guided patching.

Technical view

The issue is a heap double free in OpenSC's sc_pkcs15_free_tokeninfo function, mapped to CWE-672. The public bundle references an OSS-Fuzz report, an OpenSC commit, Gentoo advisory GLSA-202209-03, and a Debian LTS announcement. The available evidence supports a memory-management vulnerability but does not establish exploitability impact or active attacks.

Likely exposure

Organizations are likely exposed if they run vulnerable OpenSC packages, especially on endpoints, servers, or authentication systems using smart cards or PKCS#15 token handling. The bundle describes affected OpenSC before 0.22.0, but package-specific backports may change version-based conclusions.

Exploitation context

No CISA KEV listing is present, and the provided sources do not state active exploitation. The OSS-Fuzz reference suggests discovery through fuzz testing. Treat this as a memory-safety defect requiring patch validation, not as confirmed in-the-wild exploitation.

Researcher notes

Evidence is sparse: the CVE description names the function and bug class, while references indicate fuzzing, upstream commit activity, and downstream advisories. Avoid assuming remote exploitability, privilege impact, or weaponized status without reviewing linked advisories and vendor package metadata.

Mitigation direction

  • Identify systems with OpenSC installed or bundled.
  • Check vendor advisories for fixed OpenSC package versions.
  • Upgrade to vendor-supported fixed packages where available.
  • Prioritize systems using smart-card or token workflows.
  • Track Gentoo and Debian guidance for distribution-specific fixes.

Validation and detection

  • Inventory installed OpenSC versions across managed systems.
  • Confirm whether packages include vendor backported fixes.
  • Review smart-card authentication hosts for OpenSC dependency.
  • Check vulnerability scanners for CVE-2021-42778 coverage.
  • Document any exception where OpenSC cannot be upgraded.
Prepared
Confidence
medium
Sources
7

Public sources used

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-672: 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
cve · low confidence lookup

CVE-2021-42778 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aopenscopensc 0.22.0Listed
Weakness

CWE details

CWE-672

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

CWE-672 · source CWE mapping

Operation on a Resource after Expiration or Release

Operation on a Resource after Expiration or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs