Skip to content
Noroxi
CVE-2019-20792· NVD / CVE Program· CNA mitre

OpenSC before 0.20.0 has a double free in coolkey_free_private_data because coolkey_add_object in libopensc/card-coolkey.c lacks a uniquenes

Noroxi assessment

Priority: Monitor (action score 27/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.65% (FIRST EPSS); higher than 50% of all records.
  • Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: opensc (Debian:12) 0.20.0-1; opensc (openSUSE:Leap 15.2) 0.19.0-lp152.3.3.1; opensc (openSUSE:Tumbleweed) 0.22.0-3.1.

Low priority for now. Upgrade to opensc (Debian:12) 0.20.0-1; opensc (openSUSE:Leap 15.2) 0.19.0-lp152.3.3.1; opensc (openSUSE:Tumbleweed) 0.22.0-3.1 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

OpenSC before 0.20.0 has a double free in coolkey_free_private_data because coolkey_add_object in libopensc/card-coolkey.c lacks a uniqueness check.

MediumCVSS 6.8 · v3.1—No exploit Fix available
Published
Apr 29, 2020
Updated
Jun 16, 2026
EPSS
0.7% · 50th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

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.

Follow CVE-2019-20792

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for opensc project records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
opensc projectopensc

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • opensc project openscbefore 0.20.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12openscbefore 0.20.0-10.20.0-1
openSUSE:Leap 15.2openscbefore 0.19.0-lp152.3.3.10.19.0-lp152.3.3.1
openSUSE:Tumbleweedopenscbefore 0.22.0-3.10.22.0-3.1
Red Hat:enterprise_linux:8::baseosopenscbefore 0:0.20.0-2.el80:0.20.0-2.el8
Red Hat:enterprise_linux:8::baseosopensc-debuginfobefore 0:0.20.0-2.el80:0.20.0-2.el8
Red Hat:enterprise_linux:8::baseosopensc-debugsourcebefore 0:0.20.0-2.el80:0.20.0-2.el8
SUSE:Linux Enterprise High Performance Computing 15-ESPOSopenscbefore 0.18.0-150000.3.23.10.18.0-150000.3.23.1
SUSE:Linux Enterprise Module for Basesystem 15 SP2openscbefore 0.19.0-3.7.10.19.0-3.7.1

Same product

opensc project: all records

Other 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
  • CVE-2023-2977A vulnerbility was found in OpenSC.
    28Monitor
  • CVE-2025-66215OpenSC: Stack-buffer-overflow WRITE in card-oberthur
    27Monitor
  • CVE-2025-66038OpenSC: `sc_compacttlv_find_tag` can return out-of-bounds pointers
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:opensc0.20.0-1 · Debian:12Package registry (OSV)
opensuse:opensc0.19.0-lp152.3.3.1 · openSUSE:Leap 15.2Package registry (OSV)
red hat:opensc0:0.20.0-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:opensc-debuginfo0:0.20.0-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:opensc-debugsource0:0.20.0-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
suse:opensc0.19.0-3.7.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, 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.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records