DEBIAN-CVE-2025-24032
- Source
- https://security-tracker.debian.org/tracker/CVE-2025-24032
- Import Source
- https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2025-24032.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2025-24032
- Upstream
- Published
- 2025-02-10T16:15:39Z
- Modified
- 2025-10-15T07:56:39.154855Z
- Severity
-
- 9.2 (Critical) CVSS_V4 - 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X CVSS Calculator
- Summary
- [none]
- Details
-
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 certpolicy is set to none (the default value), then pampkcs11 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 leastcert_policy = signature;. - References
Affected packages
Debian:11 / pam-pkcs11
Package
- Name
- pam-pkcs11
- Purl
- pkg:deb/debian/pam-pkcs11?arch=source
Debian:12 / pam-pkcs11
Package
- Name
- pam-pkcs11
- Purl
- pkg:deb/debian/pam-pkcs11?arch=source
Debian:13 / pam-pkcs11
Package
- Name
- pam-pkcs11
- Purl
- pkg:deb/debian/pam-pkcs11?arch=source
Debian:14 / pam-pkcs11
Package
- Name
- pam-pkcs11
- Purl
- pkg:deb/debian/pam-pkcs11?arch=source