Oval Definition:oval:com.ubuntu.xenial:def:2017178050000000
Revision Date:2017-12-20Version:1
Title:CVE-2017-17805 on Ubuntu 16.04 LTS (xenial) - medium.
Description:The Salsa20 encryption algorithm in the Linux kernel before 4.14.8 does not correctly handle zero-length inputs, allowing a local attacker able to use the AF_ALG-based skcipher interface (CONFIG_CRYPTO_USER_API_SKCIPHER) to cause a denial of service (uninitialized-memory free and kernel crash) or have unspecified other impact by executing a crafted sequence of system calls that use the blkcipher_walk API. Both the generic implementation (crypto/salsa20_generic.c) and x86 implementation (arch/x86/crypto/salsa20_glue.c) of Salsa20 were vulnerable. It was discovered that the Salsa20 encryption algorithm implementations in the Linux kernel did not properly handle zero-length inputs. A local attacker could use this to cause a denial of service (system crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-17805
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-119.143').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1054.63').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1014.17').
  • 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.13.0-1012.16').
  • OR linux-gke: 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-goldfish: 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-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-38.43~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1020.25').
  • 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-119.143').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1054.63').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1014.17').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.13.0-1012.16').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-38.43~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1020.25').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1086.94').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1088.93').
  • OR linux-oem package in xenial was vulnerable but has been fixed (note: '4.13.0-1022.24').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1086.94').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-119.143').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1014.17').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.13.0-1012.16').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-38.43~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1088.93').
  • BACK