Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2025-24032

Опубликовано: 10 фев. 2025
Источник: redhat
CVSS3: 8
EPSS Низкий

Описание

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

A flaw was found in the pam_pkcs11 Linux-PAM login module. If the cert_policy is set to none, which is the default value, then pam_pkcs11 will only check if the user is capable of logging into the token. This flaw allows an attacker to create a different token with the user's public data, for example, the user's certificate and a PIN known to the attacker. If no signature with the private key is required, the attacker can log in as a user with that created token.

Отчет

This vulnerability is of moderate severity because it only applies when the configuration explicitly disables signature verification (cert_policy = none), which is not a secure best practice. The attack requires an adversary to create a fake token using the victim’s public certificate and a known PIN, but it does not compromise the private key itself. Since private key possession is typically required for strong authentication, systems enforcing proper certificate verification (including signature validation) remain unaffected. Additionally, RHEL is not vulnerable by default, further reducing the real-world impact.

Меры по смягчению последствий

Restrict the cert_policy value to signature in the pam_pkcs11.conf configuration file (cert_policy = signature).

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat Enterprise Linux 6pam_pkcs11Out of support scope
Red Hat Enterprise Linux 7pam_pkcs11Will not fix

Показывать по

Дополнительная информация

Статус:

Moderate
Дефект:
CWE-287
https://bugzilla.redhat.com/show_bug.cgi?id=2344664pam_pkcs11: PAM-PKCS#11 vulnerable to authentication bypass with default value for `cert_policy` (`none`)

EPSS

Процентиль: 50%
0.00265
Низкий

8 High

CVSS3

Связанные уязвимости

ubuntu
6 месяцев назад

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

nvd
6 месяцев назад

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

debian
6 месяцев назад

PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificat ...

CVSS3: 8
redos
29 дней назад

Уязвимость pam_pkcs11

CVSS3: 10
fstec
6 месяцев назад

Уязвимость модуля аутентификации PAM-PKCS#11 операционных систем Linux, позволяющая нарушителю обойти процесс аутентификации

EPSS

Процентиль: 50%
0.00265
Низкий

8 High

CVSS3