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;`.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade pam-pkcs11 | Feb 14, 2025 | Feb 10, 2025 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Feb 10, 2025 |
| Suse | — | Upgrade pam_pkcs11-32bitUpgrade pam_pkcs11Upgrade pam_pkcs11-devel-doc | Mar 3, 2025 | Feb 10, 2025 |
| Ubuntu | — | Upgrade libpam-pkcs11Upgrade libpam-pkcs11 (Ubuntu Pro) | Mar 21, 2025 | Feb 10, 2025 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub