CVE-2019-6133

Description

In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization decisions are improperly cached. This is related to lack of uid checking in polkitbackend/polkitbackendinteractiveauthority.c.

Category

6.7
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.02%
Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory opensuse.org Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory redhat.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://gitlab.freedesktop.org/polkit/polkit/commit/c898fdf4b1aafaa04f8ada9d73d77c8bb76e2f81 third party advisory patch
https://usn.ubuntu.com/3903-2/ third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2019:0230 third party advisory vendor advisory
https://git.kernel.org/linus/7b55851367136b1efd84d98fea81ba57a98304cf third party advisory patch
https://lists.debian.org/debian-lts-announce/2019/01/msg00021.html third party advisory mailing list
https://usn.ubuntu.com/3910-1/ third party advisory vendor advisory
https://usn.ubuntu.com/3901-2/ third party advisory vendor advisory
https://gitlab.freedesktop.org/polkit/polkit/merge_requests/19 third party advisory patch
https://bugs.chromium.org/p/project-zero/issues/detail?id=1692 issue tracking mailing list third party advisory
https://usn.ubuntu.com/3910-2/ third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2019:0420 third party advisory vendor advisory
https://usn.ubuntu.com/3908-2/ third party advisory vendor advisory
https://usn.ubuntu.com/3901-1/ third party advisory vendor advisory
https://usn.ubuntu.com/3903-1/ third party advisory vendor advisory
http://www.securityfocus.com/bid/106537 vdb entry third party advisory
https://usn.ubuntu.com/3908-1/ third party advisory vendor advisory
https://support.f5.com/csp/article/K22715344 third party advisory
https://usn.ubuntu.com/3934-1/ third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2019:0832 third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2019/05/msg00041.html mailing list
https://lists.debian.org/debian-lts-announce/2019/05/msg00042.html mailing list
http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00049.html vendor advisory
https://usn.ubuntu.com/3934-2/ vendor advisory
https://access.redhat.com/errata/RHSA-2019:2699 vendor advisory
https://access.redhat.com/errata/RHSA-2019:2978 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2019-6133?
CVE-2019-6133 has been scored as a medium severity vulnerability.
How to fix CVE-2019-6133?
To fix CVE-2019-6133, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-6133 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2019-6133 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.