Oval Definition:oval:com.ubuntu.bionic:def:201811200000000
Revision Date:2018-06-20Version:1
Title:CVE-2018-1120 on Ubuntu 18.04 LTS (bionic) - medium.
Description:A flaw was found affecting the Linux kernel before version 4.17. By mmap()ing a FUSE-backed file onto a process's memory containing command line arguments (or environment strings), an attacker can cause utilities from psutils or procps (such as ps, w) or any other program which makes a read() call to the /proc//cmdline (or /proc//environ) files to block indefinitely (denial of service) or for some controlled time (as a synchronization primitive for other attacks). It was discovered that the procfs filesystem did not properly handle processes mapping some memory elements onto files. A local attacker could use this to block utilities that examine the procfs filesystem to report operating system state, such as ps(1).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-1120
Platform(s):Ubuntu 18.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 18.04 LTS (bionic) is installed.
  • AND Package Information
  • linux package in bionic was vulnerable but has been fixed (note: '4.15.0-33.36').
  • OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1020.20').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1022.23').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1018.19').
  • OR linux-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
  • OR linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1020.20').
  • OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-33.36').
  • OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1020.20').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1022.23').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1018.19').
  • OR linux-meta-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
  • OR linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1020.20').
  • OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1017.20').
  • OR linux-meta-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
  • OR linux-meta-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1021.23').
  • 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-1017.20').
  • OR linux-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
  • OR linux-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1021.23').
  • OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-33.36').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1022.23').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1018.19').
  • OR linux-signed-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
  • OR linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1017.20').
  • OR linux-signed-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
  • OR linux-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1053.57').
  • BACK