Bug 2344664 (CVE-2025-24032) - CVE-2025-24032 pam_pkcs11: PAM-PKCS#11 vulnerable to authentication bypass with default value for `cert_policy` (`none`)
Summary: CVE-2025-24032 pam_pkcs11: PAM-PKCS#11 vulnerable to authentication bypass wi...
Keywords:
Status: NEW
Alias: CVE-2025-24032
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-10 16:01 UTC by OSIDB Bzimport
Modified: 2025-02-17 08:43 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-10 16:01:05 UTC
PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificate based user login. Prior to version 0.6.13, if cert_policy is set to none (the default value), then pam_pkcs11 will only check if the user is capable of logging into the token. An attacker may create a different token with the user's public data (e.g. the user's certificate) and a PIN known to the attacker. If no signature with the private key is required, then the attacker may now login as user with that created token. The default to *not* check the private key's signature has been changed with commit commi6638576892b59a99389043c90a1e7dd4d783b921, so that all versions starting with pam_pkcs11-0.6.0 should be affected. As a workaround, in `pam_pkcs11.conf`, set at least `cert_policy = signature;`.


Note You need to log in before you can comment on or make changes to this bug.