Bugs fixes in "policykit-1"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2021-4034 | A local privilege escalation vulnerability was found on polkit's pkexec utility. The pkexec application is a setuid tool designed to allow unprivileg | 2022-02-28 |
| CVE | CVE-2021-4115 | There is a flaw in polkit which can allow an unprivileged user to cause polkit to crash, due to process file descriptor exhaustion. The highest threa | 2022-02-28 |
| CVE | CVE-2021-4034 | A local privilege escalation vulnerability was found on polkit's pkexec utility. The pkexec application is a setuid tool designed to allow unprivileg | 2022-02-28 |
| CVE | CVE-2021-4115 | There is a flaw in polkit which can allow an unprivileged user to cause polkit to crash, due to process file descriptor exhaustion. The highest threa | 2022-02-28 |
| CVE | CVE-2021-3560 | local privilege escalation using polkit_system_bus_name_get_creds_sync() | 2021-06-03 |
| CVE | CVE-2021-3560 | local privilege escalation using polkit_system_bus_name_get_creds_sync() | 2021-06-03 |
| CVE | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization deci | 2021-05-03 |
| CVE | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization deci | 2021-05-03 |
| CVE | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization deci | 2019-04-03 |
| CVE | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization deci | 2019-04-03 |
| CVE | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization deci | 2019-04-03 |
| CVE | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization deci | 2019-04-03 |
| CVE | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization deci | 2019-04-03 |
| CVE | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization deci | 2019-04-03 |
| CVE | CVE-2018-19788 | A flaw was found in PolicyKit (aka polkit) 0.115 that allows a user with a uid greater than INT_MAX to successfully execute any systemctl command. | 2019-01-16 |
| CVE | CVE-2018-19788 | A flaw was found in PolicyKit (aka polkit) 0.115 that allows a user with a uid greater than INT_MAX to successfully execute any systemctl command. | 2019-01-16 |
| CVE | CVE-2018-19788 | A flaw was found in PolicyKit (aka polkit) 0.115 that allows a user with a uid greater than INT_MAX to successfully execute any systemctl command. | 2019-01-16 |
| CVE | CVE-2018-19788 | A flaw was found in PolicyKit (aka polkit) 0.115 that allows a user with a uid greater than INT_MAX to successfully execute any systemctl command. | 2019-01-16 |
| CVE | CVE-2018-19788 | A flaw was found in PolicyKit (aka polkit) 0.115 that allows a user with a uid greater than INT_MAX to successfully execute any systemctl command. | 2019-01-16 |
| CVE | CVE-2018-19788 | A flaw was found in PolicyKit (aka polkit) 0.115 that allows a user with a uid greater than INT_MAX to successfully execute any systemctl command. | 2019-01-16 |
About
-
Send Feedback to @ubuntu_updates
