| Revision Date: | 2019-05-08 | Version: | 1 | | Title: | CVE-2019-2054 on Ubuntu 19.04 (disco) - medium. | | Description: | In the seccomp implementation prior to kernel version 4.8, there is a possible seccomp bypass due to seccomp policies that allow the use of ptrace. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-119769499 It was discovered that the Linux kernel on ARM processors allowed a tracing process to modify a syscall after a seccomp decision had been made on that syscall. A local attacker could possibly use this to bypass seccomp restrictions.
| | Family: | unix | Class: | vulnerability | | Status: | | Reference(s): | CVE-2019-2054
| | Platform(s): | Ubuntu 19.04
| Product(s): | | | Definition Synopsis | | Ubuntu 19.04 (disco) is installed. AND Package Information
linux package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-aws package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-kvm package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-meta-aws package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-meta-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-meta-kvm package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-meta-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-meta-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1005.7').
OR linux-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1005.7').
OR linux-signed package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-signed-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-signed-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-signed-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-signed-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-snapdragon package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.10').
|
|