Improper Authentication Affecting pam-pkcs11 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Authentication vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIAN11-PAMPKCS11-8690001
  • published8 Feb 2025
  • disclosed10 Feb 2025

Introduced: 8 Feb 2025

NewCVE-2025-24032  (opens in a new tab)
CWE-287  (opens in a new tab)

How to fix?

There is no fixed version for Debian:11 pam-pkcs11.

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam-pkcs11 package and not the pam-pkcs11 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

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

CVSS Scores

version 3.1