Summary
Marcus Rückert and Matthias Gerstner discovered that PAM-PKCS#11 did not
properly handle certain return codes when authentication was not possible.
An attacker could possibly use this issue to bypass authentication. This
issue only affected Ubuntu 24.04 LTS and Ubuntu 24.10. (CVE-2025-24531)
It was discovered that PAM-PKCS#11 did not require a private key signature
for authentication by default. An attacker could possibly use this issue
to bypass authentication. (CVE-2025-24032)
Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · 20.04 LTS 20.04:LTS | pam-pkcs11 | 0.6.11-2ubuntu0.1 |
| Ubuntu · 22.04 LTS 22.04:LTS | pam-pkcs11 | 0.6.11-4ubuntu0.1 |
| Ubuntu · 24.04 LTS 24.04:LTS | pam-pkcs11 | 0.6.12-2ubuntu0.24.04.1 |
| Ubuntu · Pro 16.04 LTS Pro:16.04:LTS | pam-pkcs11 | 0.6.8-4ubuntu0.1~esm1 |
| Ubuntu · Pro 18.04 LTS Pro:18.04:LTS | pam-pkcs11 | 0.6.9-2ubuntu0.1~esm1 |
Vulnerabilities 2
-
Critical 9.2
PAM-PKCS#11 vulnerable to authentication bypass with default value for `cert_policy` (`none`)
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…
-
Medium 6.7
In OpenSC pam_pkcs11 before 0.6.13, pam_sm_authenticate() wrongly returns PAM_IGNORE in many error situations (such as …