In systemd before v242-rc4, it was discovered that pam_systemd does not properly sanitize the environment before using the XDG_SEAT variable. It is possible for an attacker, in some particular configurations, to set a XDG_SEAT environment variable which allows for commands to be checked against polkit policies using the allow_active element rather than allow_any.
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Systemd | Systemd_project | * | 241 (including) |
Systemd | Systemd_project | 242-rc1 (including) | 242-rc1 (including) |
Systemd | Systemd_project | 242-rc2 (including) | 242-rc2 (including) |
Systemd | Systemd_project | 242-rc3 (including) | 242-rc3 (including) |
Red Hat Enterprise Linux 8 | RedHat | systemd-0:239-45.el8 | * |
Red Hat Enterprise Linux 8.2 Extended Update Support | RedHat | systemd-0:239-31.el8_2.7 | * |
Systemd | Ubuntu | bionic | * |
Systemd | Ubuntu | cosmic | * |
Systemd | Ubuntu | devel | * |
Systemd | Ubuntu | trusty | * |
Systemd | Ubuntu | upstream | * |
Systemd | Ubuntu | xenial | * |
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 not applied consistently - or not at all - 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.