https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 22:21:06 +0000 https://cve.radiocsirt.org/vuln/bdu:2023-04390 bdu:2023-04390 https://cve.radiocsirt.org/vuln/bdu:2023-04390 https://cve.radiocsirt.org/vuln/euvd-2026-206208 EUVD-2026-206208 https://cve.radiocsirt.org/vuln/euvd-2026-206208 https://cve.radiocsirt.org/vuln/fkie_cve-2023-3326 <p>pam_krb5 authenticates a user by essentially running kinit with the password, getting a ticket-granting ticket (tgt) from the Kerberos KDC (Key Distribution Center) over the network, as a way to verify the password. However, if a keytab is not provisioned on the system, pam_krb5 has no way to validate the response from the KDC, and essentially trusts the tgt provided over the network as being valid. In a non-default FreeBSD installation that leverages pam_krb5 for authentication and does not have a keytab provisioned, an attacker that is able to control both the password and the KDC responses can return a valid tgt, allowing authentication to occur for any user on the system.</p> <p>pam_krb5 authenticates a user by essentially running kinit with the password, getting a ticket-granting ticket (tgt) from the Kerberos KDC (Key Distribution Center) over the network, as a way to verify the password. However, if a keytab is not provisioned on the system, pam_krb5 has no way to validate the response from the KDC, and essentially trusts the tgt provided over the network as being valid. In a non-default FreeBSD installation that leverages pam_krb5 for authentication and does not have a keytab provisioned, an attacker that is able to control both the password and the KDC responses can return a valid tgt, allowing authentication to occur for any user on the system.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-3326 https://cve.radiocsirt.org/vuln/ghsa-vjhp-527w-c5vj <p>pam_krb5 authenticates a user by essentially running kinit with the password, getting a ticket-granting ticket (tgt) from the Kerberos KDC (Key Distribution Center) over the network, as a way to verify the password. However, if a keytab is not provisioned on the system, pam_krb5 has no way to validate the response from the KDC, and essentially trusts the tgt provided over the network as being valid. In a non-default FreeBSD installation that leverages pam_krb5 for authentication and does not have a keytab provisioned, an attacker that is able to control both the password and the KDC responses can return a valid tgt, allowing authentication to occur for any user on the system.</p> <p>pam_krb5 authenticates a user by essentially running kinit with the password, getting a ticket-granting ticket (tgt) from the Kerberos KDC (Key Distribution Center) over the network, as a way to verify the password. However, if a keytab is not provisioned on the system, pam_krb5 has no way to validate the response from the KDC, and essentially trusts the tgt provided over the network as being valid. In a non-default FreeBSD installation that leverages pam_krb5 for authentication and does not have a keytab provisioned, an attacker that is able to control both the password and the KDC responses can return a valid tgt, allowing authentication to occur for any user on the system.</p> https://cve.radiocsirt.org/vuln/ghsa-vjhp-527w-c5vj https://cve.radiocsirt.org/vuln/gsd-2023-3326 gsd-2023-3326 https://cve.radiocsirt.org/vuln/gsd-2023-3326 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-3326 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: libpam-krb5, Ubuntu:16.04:LTS: libpam-krb5, Ubuntu:Pro:16.04:LTS: sssd, Ubuntu:18.04:LTS: libpam-krb5, Ubuntu:Pro:18.04:LTS: sssd, Ubuntu:20.04:LTS: libpam-krb5, Ubuntu:Pro:20.04:LTS: sssd, Ubuntu:22.04:LTS: libpam-krb5, Ubuntu:22.04:LTS: sssd, Ubuntu:24.04:LTS: libpam-krb5 and 5 more</p> <p>pam_krb5 authenticates a user by essentially running kinit with the password, getting a ticket-granting ticket (tgt) from the Kerberos KDC (Key Distribution Center) over the network, as a way to verify the password. However, if a keytab is not provisioned on the system, pam_krb5 has no way to validate the response from the KDC, and essentially trusts the tgt provided over the network as being valid. In a non-default FreeBSD installation that leverages pam_krb5 for authentication and does not have a keytab provisioned, an attacker that is able to control both the password and the KDC responses can return a valid tgt, allowing authentication to occur for any user on the system.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: libpam-krb5, Ubuntu:16.04:LTS: libpam-krb5, Ubuntu:Pro:16.04:LTS: sssd, Ubuntu:18.04:LTS: libpam-krb5, Ubuntu:Pro:18.04:LTS: sssd, Ubuntu:20.04:LTS: libpam-krb5, Ubuntu:Pro:20.04:LTS: sssd, Ubuntu:22.04:LTS: libpam-krb5, Ubuntu:22.04:LTS: sssd, Ubuntu:24.04:LTS: libpam-krb5 and 5 more</p> <p>pam_krb5 authenticates a user by essentially running kinit with the password, getting a ticket-granting ticket (tgt) from the Kerberos KDC (Key Distribution Center) over the network, as a way to verify the password. However, if a keytab is not provisioned on the system, pam_krb5 has no way to validate the response from the KDC, and essentially trusts the tgt provided over the network as being valid. In a non-default FreeBSD installation that leverages pam_krb5 for authentication and does not have a keytab provisioned, an attacker that is able to control both the password and the KDC responses can return a valid tgt, allowing authentication to occur for any user on the system.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-3326 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1518 <p>Ein entfernter Angreifer kann eine Schwachstelle in FreeBSD Project FreeBSD OS ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter Angreifer kann eine Schwachstelle in FreeBSD Project FreeBSD OS ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1518