Oval Definition:oval:com.ubuntu.bionic:def:2018121300000000
Revision Date:2019-05-30Version:1
Title:CVE-2018-12130 on Ubuntu 18.04 LTS (bionic) - high.
Description:Microarchitectural Fill Buffer Data Sampling (MFBDS): Fill buffers on some microprocessors utilizing speculative execution may allow an authenticated user to potentially enable information disclosure via a side channel with local access. A list of impacted products can be found here: https://www.intel.com/content/dam/www/public/us/en/documents/corporate-information/SA00233-microcode-update-guidance_05132019.pdf Ke Sun, Henrique Kawakami, Kekai Hu, Rodrigo Branco, Giorgi Maisuradze, Dan Horea Lutas, Andrei Lutas, Volodymyr Pikhur, Stephan van Schaik, Alyssa Milburn, Sebastian Ă–sterlund, Pietro Frigo, Kaveh Razavi, Herbert Bos, Cristiano Giuffrida, Moritz Lipp, Michael Schwarz, and Daniel Gruss discovered that memory previously stored in microarchitectural fill buffers of an Intel CPU core may be exposed to a malicious process that is executing on the same CPU core. A local attacker could use this to expose sensitive information.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-12130
Platform(s):Ubuntu 18.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 18.04 LTS (bionic) is installed.
  • AND Package Information
  • intel-microcode package in bionic was vulnerable but has been fixed (note: '3.20190514.0ubuntu0.18.04.2').
  • OR libvirt package in bionic was vulnerable but has been fixed (note: '4.0.0-1ubuntu8.10').
  • OR linux package in bionic was vulnerable but has been fixed (note: '4.15.0-50.54').
  • OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1039.41').
  • OR linux-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '4.18.0-1018.18~18.04.1').
  • OR linux-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1032.34').
  • OR linux-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1032.34').
  • OR linux-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-hwe package in bionic was vulnerable but has been fixed (note: '4.18.0-20.21~18.04.1').
  • OR linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1034.34').
  • OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-50.54').
  • OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1039.41').
  • OR linux-meta-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '4.18.0-1018.18~18.04.1').
  • OR linux-meta-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1032.34').
  • OR linux-meta-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-meta-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1032.34').
  • OR linux-meta-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-meta-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-meta-hwe package in bionic was vulnerable but has been fixed (note: '4.18.0-20.21~18.04.1').
  • OR linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1034.34').
  • OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1038.43').
  • OR linux-meta-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • OR linux-meta-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1013.15').
  • OR linux-meta-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-meta-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1036.38').
  • OR linux-meta-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
  • OR linux-meta-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1053.57').
  • OR linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1038.43').
  • OR linux-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • OR linux-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1013.15').
  • OR linux-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1036.38').
  • OR linux-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
  • OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-50.54').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '4.18.0-1018.18~18.04.1').
  • OR linux-signed-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1032.34').
  • OR linux-signed-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-signed-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1032.34').
  • OR linux-signed-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-signed-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-signed-hwe package in bionic was vulnerable but has been fixed (note: '4.18.0-20.21~18.04.1').
  • OR linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1038.43').
  • OR linux-signed-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • OR linux-signed-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1013.15').
  • OR linux-signed-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1053.57').
  • OR qemu package in bionic was vulnerable but has been fixed (note: '1:2.11+dfsg-1ubuntu7.13').
  • BACK