MEDIUM · 6.7

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 decisions are improperly cached. This is related to lac...

Vulnerability 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.

CVSS Score

6.7

MEDIUM

CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH

Affected Products

VendorProductVersions
Polkit ProjectPolkit0.115
DebianDebian Linux8.0
RedhatEnterprise Linux Desktop7.0
RedhatEnterprise Linux Server7.0
RedhatEnterprise Linux Server Aus7.6
RedhatEnterprise Linux Server Eus7.6
RedhatEnterprise Linux Server Tus7.6
RedhatEnterprise Linux Workstation7.0
CanonicalUbuntu Linux12.04

Related Weaknesses (CWE)

References

FAQ

What is CVE-2019-6133?

CVE-2019-6133 is a vulnerability with a CVSS score of 6.7 (MEDIUM). 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 lac...

How severe is CVE-2019-6133?

CVE-2019-6133 has been rated MEDIUM with a CVSS base score of 6.7/10. Review the CVSS metrics above for detailed severity breakdown.

Is there a patch for CVE-2019-6133?

Check the references section above for vendor advisories and patch information. Affected products include: Polkit Project Polkit, Debian Debian Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus.