PIN bypass via cached token authentication
Published Nov 6, 2023 · Updated Nov 6, 2025
Improper authentication in OpenSC 0.17.0 through 0.23.0 allows physically proximate attackers to bypass a smart-card PIN. The sc_pkcs15_verify_pin function treats an empty PIN as successful when the card reports a cached logged-in state left by another process. Exploitation requires a connected, previously authenticated token and an application that accepts an empty PIN, enabling unauthorized signing, decryption, or OS unlock.
Summary
What happened
Improper authentication in OpenSC 0.17.0 through 0.23.0 allows physically proximate attackers to bypass a smart-card PIN. The sc_pkcs15_verify_pin function treats an empty PIN as successful when the card reports a cached logged-in state left by another process. Exploitation requires a connected, previously authenticated token and an application that accepts an empty PIN, enabling unauthorized signing, decryption, or OS unlock.
The record
- CVE
- CVE-2023-40660
- Published
- Nov 6, 2023
- Updated
- Nov 6, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-287
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 6, 2023CVE publishedPublication date reported by the CVE source.
- Nov 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo