Sudo before 1.9.17p1, when used with a sudoers file that specifies a host that is neither the current host nor ALL, allows listed users to execute commands on unintended machines.
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Red Hat Enterprise Linux 8 | RedHat | sudo-0:1.9.5p2-1.el8_10.1 | * |
Red Hat Enterprise Linux 9 | RedHat | sudo-0:1.9.5p2-10.el9_6.1 | * |
Red Hat Enterprise Linux 9 | RedHat | sudo-0:1.9.5p2-10.el9_6.1 | * |
Sudo | Ubuntu | devel | * |
Sudo | Ubuntu | esm-infra-legacy/trusty | * |
Sudo | Ubuntu | esm-infra/bionic | * |
Sudo | Ubuntu | esm-infra/focal | * |
Sudo | Ubuntu | esm-infra/xenial | * |
Sudo | Ubuntu | jammy | * |
Sudo | Ubuntu | noble | * |
Sudo | Ubuntu | oracular | * |
Sudo | Ubuntu | plucky | * |
Sudo | Ubuntu | upstream | * |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are incorrectly applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.