| VuXML ID | Description |
|---|
| b3435b68-9ee8-11e1-997c-002354ed89bc | sudo -- netmask vulnerability
Todd Miller reports:
Sudo supports granting access to commands on a per-host basis.
The host specification may be in the form of a host name, a
netgroup, an IP address, or an IP network (an IP address with an
associated netmask).
When IPv6 support was added to sudo, a bug was introduced that
caused the IPv6 network matching code to be called when an IPv4
network address does not match. Depending on the value of the
uninitialized portion of the IPv6 address, it is possible for the
IPv4 network number to match when it should not. This bug only
affects IP network matching and does not affect simple IP address
matching.
The reported configuration that exhibited the bug was an
LDAP-based sudo installation where the sudoRole object contained
multiple sudoHost entries, each containing a different IPv4
network. File-based sudoers should be affected as well as the
same matching code is used.
Discovery 2012-05-16
Entry 2012-05-16
sudo
le 1.8.4_1
CVE-2012-2337
http://www.sudo.ws/sudo/alerts/netmask.html
|
| b3435b68-9ee8-11e1-997c-002354ed89bc | sudo -- netmask vulnerability
Todd Miller reports:
Sudo supports granting access to commands on a per-host basis.
The host specification may be in the form of a host name, a
netgroup, an IP address, or an IP network (an IP address with an
associated netmask).
When IPv6 support was added to sudo, a bug was introduced that
caused the IPv6 network matching code to be called when an IPv4
network address does not match. Depending on the value of the
uninitialized portion of the IPv6 address, it is possible for the
IPv4 network number to match when it should not. This bug only
affects IP network matching and does not affect simple IP address
matching.
The reported configuration that exhibited the bug was an
LDAP-based sudo installation where the sudoRole object contained
multiple sudoHost entries, each containing a different IPv4
network. File-based sudoers should be affected as well as the
same matching code is used.
Discovery 2012-05-16
Entry 2012-05-16
sudo
le 1.8.4_1
CVE-2012-2337
http://www.sudo.ws/sudo/alerts/netmask.html
|
| 82cfd919-8213-11e2-9273-902b343deec9 | sudo -- Potential bypass of tty_tickets constraints
Todd Miller reports:
A (potentially malicious) program run by a user with sudo access
may be able to bypass the "tty_ticket" constraints. In order for
this to succeed there must exist on the machine a terminal device
that the user has previously authenticated themselves on via sudo
within the last time stamp timeout (5 minutes by default).
Discovery 2013-02-27
Entry 2013-03-01
sudo
lt 1.8.6.p7
CVE-2013-1776
http://www.sudo.ws/sudo/alerts/tty_tickets.html
|
| 908f4cf2-1e8b-11e0-a587-001b77d09812 | sudo -- local privilege escalation
Todd Miller reports:
Beginning with sudo version 1.7.0 it has been possible
to grant permission to run a command using a specified
group via sudo's -g option (run as group), if allowed by
the sudoers file. A flaw exists in sudo's password
checking logic that allows a user to run a command
with only the group changed without being prompted
for a password.
Discovery 2011-01-11
Entry 2011-01-13
sudo
ge 1.7.0 lt 1.7.4.5
CVE-2011-0010
http://www.sudo.ws/sudo/alerts/runas_group_pw.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609641
|
| 908f4cf2-1e8b-11e0-a587-001b77d09812 | sudo -- local privilege escalation
Todd Miller reports:
Beginning with sudo version 1.7.0 it has been possible
to grant permission to run a command using a specified
group via sudo's -g option (run as group), if allowed by
the sudoers file. A flaw exists in sudo's password
checking logic that allows a user to run a command
with only the group changed without being prompted
for a password.
Discovery 2011-01-11
Entry 2011-01-13
sudo
ge 1.7.0 lt 1.7.4.5
CVE-2011-0010
http://www.sudo.ws/sudo/alerts/runas_group_pw.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609641
|
| 764344fb-8214-11e2-9273-902b343deec9 | sudo -- Authentication bypass when clock is reset
Todd Miller reports:
The flaw may allow someone with physical access to a machine that
is not password-protected to run sudo commands without knowing the
logged in user's password. On systems where sudo is the principal
way of running commands as root, such as on Ubuntu and Mac OS X,
there is a greater chance that the logged in user has run sudo
before and thus that an attack would succeed.
Discovery 2013-02-27
Entry 2013-03-01
sudo
lt 1.8.6.p7
CVE-2013-1775
http://www.sudo.ws/sudo/alerts/epoch_ticket.html
|