| Revision Date: | 2014-07-03 | Version: | 1 | | Title: | CVE-2014-4611 on Ubuntu 18.04 LTS (bionic) - medium. | | Description: | Integer overflow in the LZ4 algorithm implementation, as used in Yann Collet LZ4 before r118 and in the lz4_uncompress function in lib/lz4/lz4_decompress.c in the Linux kernel before 3.15.2, on 32-bit platforms might allow context-dependent attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted Literal Run that would be improperly handled by programs not complying with an API limitation, a different vulnerability than CVE-2014-4715. Don Bailey and Ludvig Strigeus discovered an integer overflow in the Linux kernel's implementation of the LZ4 decompression algorithm, when used by code not complying with API limitations. An attacker could exploit this flaw to cause a denial of service (memory corruption) or possibly other unspecified impact.
| | Family: | unix | Class: | vulnerability | | Status: | | Reference(s): | CVE-2014-4611
| | Platform(s): | Ubuntu 18.04 LTS
| Product(s): | | | Definition Synopsis | | Ubuntu 18.04 LTS (bionic) is installed. AND Package Information
linux package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
OR linux-aws package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
OR linux-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
OR linux-azure package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
OR linux-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
OR linux-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
OR linux-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
OR linux-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
OR linux-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
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, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-meta package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
OR linux-meta-aws package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
OR linux-meta-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
OR linux-meta-azure package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-meta-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
OR linux-meta-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
OR linux-meta-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
OR linux-meta-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
OR linux-meta-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
OR linux-meta-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
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, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-meta-oem package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
OR linux-meta-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
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-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
OR linux-meta-raspi2 package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-1005.5').
OR linux-meta-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
OR linux-meta-snapdragon package in bionic, is related to the CVE in some way and has been fixed (note: '4.4.0-1077.82').
OR linux-oem package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
OR linux-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
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-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
OR linux-raspi2 package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-1005.5').
OR linux-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
OR linux-signed package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
OR linux-signed-azure package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
OR linux-signed-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
OR linux-signed-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
OR linux-signed-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
OR linux-signed-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
OR linux-signed-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
OR linux-signed-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
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, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
OR linux-signed-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
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-signed-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
OR linux-snapdragon package in bionic, is related to the CVE in some way and has been fixed (note: '4.4.0-1077.82').
OR lz4 package in bionic, is related to the CVE in some way and has been fixed (note: '0.0~r118-1').
|
|