Oval Definition:oval:com.ubuntu.xenial:def:201836930000000
Revision Date:2018-07-10Version:1
Title:CVE-2018-3693 on Ubuntu 16.04 LTS (xenial) - high.
Description:Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a speculative buffer overflow and side-channel analysis.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-3693
Platform(s):Ubuntu 16.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 16.04 LTS (xenial) is installed.
  • AND Package Information
  • firefox package in xenial, is related to the CVE in some way and has been fixed (note: '63.0+build2-0ubuntu0.16.04.2').
  • OR intel-microcode package in xenial was vulnerable but has been fixed (note: '3.20180312.0~ubuntu16.04.1').
  • OR linux package in xenial was vulnerable but has been fixed (note: '4.4.0-112.135').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1049.58').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-euclid package in xenial was vulnerable but has been fixed (note: '4.4.0-9023.24').
  • 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-1014.14~16.04.1').
  • 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.15.0-24.26~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1017.22').
  • 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-112.135').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1049.58').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1014.14~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1017.22').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1085.93').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1087.92').
  • 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-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1085.93').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-112.135').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1014.14~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1087.92').
  • BACK