Oval Definition:oval:com.ubuntu.xenial:def:201961330000000
Revision Date:2019-01-11Version:1
Title:CVE-2019-6133 on Ubuntu 16.04 LTS (xenial) - medium.
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. Jann Horn discovered a race condition in the fork() system call in the Linux kernel. A local attacker could use this to gain access to services that cache authorizations.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-6133
Platform(s):Ubuntu 16.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 16.04 LTS (xenial) is installed.
  • AND Package Information
  • linux package in xenial was vulnerable but has been fixed (note: '4.4.0-143.169').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1077.87').
  • OR linux-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1033.35~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1040.44').
  • OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed ESM criteria').
  • OR linux-flo: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'abandoned').
  • OR linux-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1028.29~16.04.1').
  • OR linux-gke: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life').
  • OR linux-goldfish: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-46.49~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1041.47').
  • OR linux-mako: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'abandoned').
  • OR linux-meta package in xenial was vulnerable but has been fixed (note: '4.4.0-143.169').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1077.87').
  • OR linux-meta-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1033.35~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1040.44').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1028.29~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-46.49~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1041.47').
  • OR linux-meta-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1009.11~16.04.1').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1104.112').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1108.113').
  • OR linux-oem: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage now end-of-life').
  • OR linux-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1009.11~16.04.1').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1104.112').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-143.169').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1040.44').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1028.29~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-46.49~16.04.1').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1009.11~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1108.113').
  • OR policykit-1 package in xenial was vulnerable but has been fixed (note: '0.105-14.1ubuntu0.5').
  • BACK