Skip to main content
No exploitation reportedFix available

CVE-2023-40660

Opensc: potential pin bypass when card tracks its own login state

No exploitation reported by the sources we read.

  • Published2023-11-06
  • WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A flaw was found in OpenSC packages that allow a potential PIN bypass. When a token/card is authenticated by one process, it can perform cryptographic operations in other processes when an empty zero-length pin is passed. This issue poses a security risk, particularly for OS logon/screen unlock and for small, permanently connected tokens to computers. Additionally, the token can internally track login status. This flaw allows an attacker to gain unauthorized access, carry out malicious actions, or compromise the system without the user's awareness.

Timeline

dates in UTC
  1. 2023-11-0616:58CVE publishedCNA

Versions per branch

NVD
Redhat enterprise linux
BranchAffectedFixed in
8.0= 8.0no fix published
9.0= 9.0no fix published
Opensc project opensc
BranchAffectedFixed in
0.23≤ 0.23.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA4 products

As redhat, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-06

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • openscUbuntu:Pro:24.04:LTSall versions · fixed in 0.25.0~rc1-1ubuntu0.1~esm1
  • openscUbuntu:Pro:22.04:LTSall versions · fixed in 0.22.0-1ubuntu2+esm1
  • openscUbuntu:Pro:20.04:LTSall versions · fixed in 0.20.0-3ubuntu0.1~esm4
  • openscUbuntu:Pro:20.04:LTSall versions · fixed in 0.20.0-3ubuntu0.1~esm2
  • openscUbuntu:Pro:18.04:LTSall versions · fixed in 0.17.0-3ubuntu0.1~esm2
  • openscUbuntu:Pro:16.04:LTSall versions · fixed in 0.15.0-1ubuntu1+esm2
  • openscTuxCare:AlmaLinux:9.2all versions · fixed in 0.22.0-2.el9_2.tuxcare.els7
  • openscSUSE:Manager Server 4.2all versions · fixed in 0.19.0-150100.3.25.1

40 more package ranges on OSV.dev

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2023-11-06
Last Modified
2026-11-06
NVD status
Modified
GitHub Advisory
GHSA-7635-x5f9-5458

Frequently asked questions

What is CVE-2023-40660?

A flaw was found in OpenSC packages that allow a potential PIN bypass. When a token/card is authenticated by one process, it can perform cryptographic operations in other processes when an empty zero-length pin is passed. This issue poses a security risk, particularly for OS logon/screen unlock and for small, permanently connected tokens to computers. Additionally, the token can internally track login status. This flaw allows an attacker to gain unauthorized access, carry out malicious actions, or compromise the system without the user's awareness.

Is CVE-2023-40660 actively exploited?

Active exploitation of CVE-2023-40660 has not been confirmed. Its EPSS score was 1.0% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-40660?

CVE-2023-40660 has a CVSS v3 base score of 6.6 (MEDIUM severity), with vector string CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running opensc? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record