Oval Definition:oval:com.ubuntu.xenial:def:2018146330000000
Revision Date:2018-09-25Version:1
Title:CVE-2018-14633 on Ubuntu 16.04 LTS (xenial) - medium.
Description:A security flaw was found in the chap_server_compute_md5() function in the ISCSI target code in the Linux kernel in a way an authentication request from an ISCSI initiator is processed. An unauthenticated remote attacker can cause a stack buffer overflow and smash up to 17 bytes of the stack. The attack requires the iSCSI target to be enabled on the victim host. Depending on how the target's code was built (i.e. depending on a compiler, compile flags and hardware architecture) an attack may lead to a system crash and thus to a denial-of-service or possibly to a non-authorized access to data exported by an iSCSI target. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is highly unlikely. Kernel versions 4.18.x, 4.14.x and 3.10.x are believed to be vulnerable. It was discovered that a stack-based buffer overflow existed in the iSCSI target implementation of the Linux kernel. A remote attacker could use this to cause a denial of service (system crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-14633
Platform(s):Ubuntu 16.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 16.04 LTS (xenial) is installed.
  • AND Package Information
  • linux package in xenial was vulnerable but has been fixed (note: '4.4.0-137.163').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1069.79').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1025.26~16.04.1').
  • OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed 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.15.0-1021.22~16.04.1').
  • OR linux-gke: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life').
  • OR linux-goldfish: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-36.39~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1035.41').
  • 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-137.163').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1069.79').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1025.26~16.04.1').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1021.22~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-36.39~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1035.41').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1098.106').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1102.107').
  • OR linux-oem: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed now end-of-life').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1098.106').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-137.163').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1025.26~16.04.1').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1021.22~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-36.39~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1102.107').
  • BACK