Oval Definition:oval:com.ubuntu.bionic:def:2018189550000000
Revision Date:2018-11-16Version:1
Title:CVE-2018-18955 on Ubuntu 18.04 LTS (bionic) - medium.
Description:In the Linux kernel 4.15.x through 4.19.x before 4.19.2, map_write() in kernel/user_namespace.c allows privilege escalation because it mishandles nested user namespaces with more than 5 UID or GID ranges. A user who has CAP_SYS_ADMIN in an affected user namespace can bypass access controls on resources outside the namespace, as demonstrated by reading /etc/shadow. This occurs because an ID transformation takes place properly for the namespaced-to-kernel direction but not for the kernel-to-namespaced direction. Jann Horn discovered that the Linux kernel mishandles mapping UID or GID ranges inside nested user namespaces in some situations. A local attacker could use this to bypass access controls on resources outside the namespace.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-18955
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-42.45').
  • OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.30').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1035.36').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1025.26').
  • 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-1027.27').
  • OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-42.45').
  • OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.30').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1035.36').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1025.26').
  • 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-1027.27').
  • OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1028.33').
  • 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-1029.31').
  • OR linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1028.33').
  • 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-1029.31').
  • OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-42.45').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '4.15.0-1035.36').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1025.26').
  • 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-1028.33').
  • 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').
  • BACK