Oval Definition:oval:com.ubuntu.xenial:def:201836390000000
Revision Date:2018-05-22Version:1
Title:CVE-2018-3639 on Ubuntu 16.04 LTS (xenial) - medium.
Description:Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka Speculative Store Bypass (SSB), Variant 4. Jann Horn and Ken Johnson discovered that microprocessors utilizing speculative execution of a memory read may allow unauthorized memory reads via a sidechannel attack. This flaw is known as Spectre Variant 4. A local attacker could use this to expose sensitive information, including kernel memory.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-3639
Platform(s):Ubuntu 16.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 16.04 LTS (xenial) is installed.
  • AND Package Information
  • intel-microcode package in xenial was vulnerable but has been fixed (note: '3.20180807a.0ubuntu0.16.04.1').
  • OR libvirt package in xenial was vulnerable but has been fixed (note: '1.3.1-1ubuntu10.24').
  • OR linux package in xenial was vulnerable but has been fixed (note: '4.4.0-127.153').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1060.69').
  • OR linux-aws-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.31~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1018.21').
  • OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage 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.13.0-1017.21').
  • OR linux-gke: 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-goldfish: 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-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-43.48~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1026.31').
  • 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-127.153').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1060.69').
  • OR linux-meta-aws-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.31~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1018.21').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.13.0-1017.21').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-43.48~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1026.31').
  • OR linux-meta-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1091.99').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1094.99').
  • OR linux-oem package in xenial was vulnerable but has been fixed (note: '4.13.0-1028.31').
  • OR linux-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1091.99').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-127.153').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1018.21').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.13.0-1017.21').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-43.48~16.04.1').
  • OR linux-signed-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1094.99').
  • OR qemu package in xenial was vulnerable but has been fixed (note: '1:2.5+dfsg-5ubuntu10.29').
  • BACK