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;`.
History

Tue, 18 Feb 2025 14:45:00 +0000

Type Values Removed Values Added
References

Mon, 17 Feb 2025 15:15:00 +0000

Type Values Removed Values Added
Metrics threat_severity

Important

threat_severity

Moderate


Wed, 12 Feb 2025 16:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 11 Feb 2025 13:45:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 8.0, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L'}

threat_severity

Important


Mon, 10 Feb 2025 16:00:00 +0000

Type Values Removed Values Added
Description 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;`.
Title PAM-PKCS#11 vulnerable to authentication bypass with default value for `cert_policy` (`none`)
Weaknesses CWE-287
References
Metrics cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:L/SA:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2025-02-18T13:06:30.133Z

Reserved: 2025-01-16T17:31:06.460Z

Link: CVE-2025-24032

cve-icon Vulnrichment

Updated: 2025-02-18T13:06:30.133Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-02-10T16:15:39.153

Modified: 2025-02-18T14:15:28.770

Link: CVE-2025-24032

cve-icon Redhat

Severity : Moderate

Publid Date: 2025-02-10T15:43:47Z

Links: CVE-2025-24032 - Bugzilla