https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 23:37:40 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-09007 bdu:2025-09007 https://cve.radiocsirt.org/vuln/bdu:2025-09007 https://cve.radiocsirt.org/vuln/euvd-2026-240678 EUVD-2026-240678 https://cve.radiocsirt.org/vuln/euvd-2026-240678 https://cve.radiocsirt.org/vuln/fkie_cve-2025-24032 <p>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&#39;s public data (e.g. the user&#39;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&#39;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;`.</p> <p>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&#39;s public data (e.g. the user&#39;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&#39;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;`.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-24032 https://cve.radiocsirt.org/vuln/opensuse-su-2025:14738-1 <p>pam_pkcs11-0.6.13-1.1 on GA media</p> <p>pam_pkcs11-0.6.13-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:14738-1 https://cve.radiocsirt.org/vuln/suse-su-2025:0688-1 <p>Security update for pam_pkcs11</p> <p>Security update for pam_pkcs11</p> https://cve.radiocsirt.org/vuln/suse-su-2025:0688-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-24032 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: pam-pkcs11, Ubuntu:Pro:18.04:LTS: pam-pkcs11, Ubuntu:20.04:LTS: pam-pkcs11, Ubuntu:22.04:LTS: pam-pkcs11, Ubuntu:24.04:LTS: pam-pkcs11</p> <p>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&#39;s public data (e.g. the user&#39;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&#39;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;`.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: pam-pkcs11, Ubuntu:Pro:18.04:LTS: pam-pkcs11, Ubuntu:20.04:LTS: pam-pkcs11, Ubuntu:22.04:LTS: pam-pkcs11, Ubuntu:24.04:LTS: pam-pkcs11</p> <p>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&#39;s public data (e.g. the user&#39;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&#39;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;`.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-24032