Oval Definition:oval:com.ubuntu.disco:def:201961330000000
Revision Date:2019-01-11Version:1
Title:CVE-2019-6133 on Ubuntu 19.04 (disco) - 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 19.04
Product(s):
Definition Synopsis
  • Ubuntu 19.04 (disco) is installed.
  • AND Package Information
  • linux package in disco, is related to the CVE in some way and has been fixed (note: '4.19.0-12.13').
  • OR linux-aws package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1011.13').
  • OR linux-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1013.13').
  • OR linux-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1007.8').
  • OR linux-kvm package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1008.8').
  • OR linux-meta package in disco, is related to the CVE in some way and has been fixed (note: '4.19.0-12.13').
  • OR linux-meta-aws package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1011.13').
  • OR linux-meta-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1013.13').
  • OR linux-meta-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1007.8').
  • OR linux-meta-kvm package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1008.8').
  • OR linux-meta-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1034.39').
  • OR linux-meta-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1009.11').
  • OR linux-meta-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1010.12').
  • OR linux-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1034.39').
  • OR linux-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1009.11').
  • OR linux-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1010.12').
  • OR linux-signed package in disco, is related to the CVE in some way and has been fixed (note: '4.19.0-12.13').
  • OR linux-signed-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1013.13').
  • OR linux-signed-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1007.8').
  • OR linux-signed-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1034.39').
  • OR linux-signed-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1009.11').
  • OR linux-snapdragon package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.10').
  • OR policykit-1 package in disco was vulnerable but has been fixed (note: '0.105-25').
  • BACK