Skip to content
Fencer Vulns
low 2.1

CVE-2009-0368 json

OpenSC before 0.11.7 allows physically proximate attackers to bypass intended PIN requirements and read private data objects via a (1) low…

published 2009-03-02 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0372

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
1
Exploit-DB

Summary

OpenSC before 0.11.7 allows physically proximate attackers to bypass intended PIN requirements and read private data objects via a (1) low level APDU command or (2) debugging tool, as demonstrated by reading the 4601 or 4701 file with the opensc-explorer or opensc-tool program.

Patch / fix

  • opensc Debian 14, Debian 13, Debian 12 0.11.7-1

debian advisories DEBIAN-CVE-2009-0368

  • opensc openSUSE Tumbleweed 0.16.0-2.1

opensuse advisories openSUSE-SU-2024:10269-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-0368 updated

opensc: insufficient access restrictions on private data

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-32820)
  2. Published

Exploit prediction

1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-32820 OpenSC 0.11.x - PKCS#11 Implementation Unauthorized Access local, 2009-02-26
  • securityfocus.com http://www.securityfocus.com/bid/33922 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.