Vulnerability & Exploit Database

Displaying all 6 entries

Results for: CVE-2019-6133 Back to search

Ubuntu: (Multiple Advisories) (CVE-2019-6133): Linux kernel (HWE) vulnerabilities Vulnerability

  • Severity: 4
  • Published: January 11, 2019

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.

Red Hat: CVE-2019-6133: Important: polkit security update (Multiple Advisories) Vulnerability

  • Severity: 4
  • Published: January 11, 2019

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.

Oracle Linux: (CVE-2019-6133) (Multiple Advisories): polkit security update Vulnerability

  • Severity: 4
  • Published: January 11, 2019

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.

Huawei EulerOS: CVE-2019-6133: polkit security update Vulnerability

  • Severity: 4
  • Published: January 11, 2019

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.

Debian: CVE-2019-6133: policykit-1 -- security update Vulnerability

  • Severity: 4
  • Published: January 11, 2019

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.

CentOS: (CVE-2019-6133) (Multiple Advisories): polkit Vulnerability

  • Severity: 4
  • Published: January 11, 2019

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.