Skip to main content
CVE-2023-40660VulnerabilityPublished Updated

CVE-2023-40660: Improper Authentication

Source CVE Database V5

0

Not known to be exploited · CVSS 6.6 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

1. Monitor OpenSC project communications and promptly apply patches or updates once they become available to address CVE-2023-40660. 2. Until patched versions are deployed, restrict physical and logical access to systems using OpenSC tokens to trusted personnel only. 3. Implement strict access controls and endpoint security measures to prevent unauthorized local access. 4. Audit and monitor authentication logs for unusual or repeated authentication attempts involving smart cards or tokens. 5. Consider temporarily disabling or limiting the use of smart card authentication for OS logon or screen unlock on high-risk systems. 6. Employ additional layers of security such as hardware security modules (HSMs) or multi-factor authentication methods that do not rely solely on OpenSC tokens. 7. Educate users and administrators about the risk of token misuse and the importance of safeguarding authentication devices. 8. Conduct regular security assessments and penetration tests focusing on smart card authentication mechanisms to detect potential exploitation attempts.

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.

References

Community reviews

Loading reviews…