https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 14:29:03 +0000 https://cve.radiocsirt.org/vuln/bdu:2020-00856 bdu:2020-00856 https://cve.radiocsirt.org/vuln/bdu:2020-00856 https://cve.radiocsirt.org/vuln/bell-cve-2019-19234 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2019-19234 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0504 certfr-2023-avi-0504 https://cve.radiocsirt.org/vuln/certfr-2023-avi-0504 https://cve.radiocsirt.org/vuln/euvd-2026-59149 EUVD-2026-59149 https://cve.radiocsirt.org/vuln/euvd-2026-59149 https://cve.radiocsirt.org/vuln/fkie_cve-2019-19234 <p>In Sudo through 1.8.29, the fact that a user has been blocked (e.g., by using the ! character in the shadow file instead of a password hash) is not considered, allowing an attacker (who has access to a Runas ALL sudoer account) to impersonate any blocked user. NOTE: The software maintainer believes that this CVE is not valid. Disabling local password authentication for a user is not the same as disabling all access to that user--the user may still be able to login via other means (ssh key, kerberos, etc). Both the Linux shadow(5) and passwd(1) manuals are clear on this. Indeed it is a valid use case to have local accounts that are _only_ accessible via sudo and that cannot be logged into with a password. Sudo 1.8.30 added an optional setting to check the _shell_ of the target user (not the encrypted password!) against the contents of /etc/shells but that is not the same thing as preventing access to users with an invalid password hash</p> <p>In Sudo through 1.8.29, the fact that a user has been blocked (e.g., by using the ! character in the shadow file instead of a password hash) is not considered, allowing an attacker (who has access to a Runas ALL sudoer account) to impersonate any blocked user. NOTE: The software maintainer believes that this CVE is not valid. Disabling local password authentication for a user is not the same as disabling all access to that user--the user may still be able to login via other means (ssh key, kerberos, etc). Both the Linux shadow(5) and passwd(1) manuals are clear on this. Indeed it is a valid use case to have local accounts that are _only_ accessible via sudo and that cannot be logged into with a password. Sudo 1.8.30 added an optional setting to check the _shell_ of the target user (not the encrypted password!) against the contents of /etc/shells but that is not the same thing as preventing access to users with an invalid password hash</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-19234 https://cve.radiocsirt.org/vuln/ghsa-vh47-792w-24m4 <p>In Sudo through 1.8.29, the fact that a user has been blocked (e.g., by using the ! character in the shadow file instead of a password hash) is not considered, allowing an attacker (who has access to a Runas ALL sudoer account) to impersonate any blocked user.</p> <p>In Sudo through 1.8.29, the fact that a user has been blocked (e.g., by using the ! character in the shadow file instead of a password hash) is not considered, allowing an attacker (who has access to a Runas ALL sudoer account) to impersonate any blocked user.</p> https://cve.radiocsirt.org/vuln/ghsa-vh47-792w-24m4 https://cve.radiocsirt.org/vuln/gsd-2019-19234 gsd-2019-19234 https://cve.radiocsirt.org/vuln/gsd-2019-19234 https://cve.radiocsirt.org/vuln/rhsa-2020:1804 <p>sudo: attacker with access to a Runas ALL sudoer account can impersonate a nonexistent user sudo: by using ! character in the shadow file instead of a password hash can access to a run as all sudoer account</p> <p>sudo: attacker with access to a Runas ALL sudoer account can impersonate a nonexistent user sudo: by using ! character in the shadow file instead of a password hash can access to a run as all sudoer account</p> https://cve.radiocsirt.org/vuln/rhsa-2020:1804 https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-19234 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: sudo</p> <p>In Sudo through 1.8.29, the fact that a user has been blocked (e.g., by using the ! character in the shadow file instead of a password hash) is not considered, allowing an attacker (who has access to a Runas ALL sudoer account) to impersonate any blocked user. NOTE: The software maintainer believes that this CVE is not valid. Disabling local password authentication for a user is not the same as disabling all access to that user--the user may still be able to login via other means (ssh key, kerberos, etc). Both the Linux shadow(5) and passwd(1) manuals are clear on this. Indeed it is a valid use case to have local accounts that are _only_ accessible via sudo and that cannot be logged into with a password. Sudo 1.8.30 added an optional setting to check the _shell_ of the target user (not the encrypted password!) against the contents of /etc/shells but that is not the same thing as preventing access to users with an invalid password hash</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: sudo</p> <p>In Sudo through 1.8.29, the fact that a user has been blocked (e.g., by using the ! character in the shadow file instead of a password hash) is not considered, allowing an attacker (who has access to a Runas ALL sudoer account) to impersonate any blocked user. NOTE: The software maintainer believes that this CVE is not valid. Disabling local password authentication for a user is not the same as disabling all access to that user--the user may still be able to login via other means (ssh key, kerberos, etc). Both the Linux shadow(5) and passwd(1) manuals are clear on this. Indeed it is a valid use case to have local accounts that are _only_ accessible via sudo and that cannot be logged into with a password. Sudo 1.8.30 added an optional setting to check the _shell_ of the target user (not the encrypted password!) against the contents of /etc/shells but that is not the same thing as preventing access to users with an invalid password hash</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-19234 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1600 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in sudo ausnutzen, um seine Privilegien zu erhöhen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in sudo ausnutzen, um seine Privilegien zu erhöhen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1600