Oval Definition:
oval:com.ubuntu.bionic:def:2019195330000000
Revision Date
:
2019-12-03
Version
:
1
Title
:
CVE-2019-19533 on Ubuntu 18.04 LTS (bionic) - low.
Description
:
In the Linux kernel before 5.3.4, there is an info-leak bug that can be caused by a malicious USB device in the drivers/media/usb/ttusb-dec/ttusb_dec.c driver, aka CID-a10feaf8c464.
Family
:
unix
Class
:
vulnerability
Status
:
Reference(s)
:
CVE-2019-19533
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-69.78').
OR
linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1054.56').
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 was vulnerable but has been fixed (note: '5.0.0-1025.27~18.04.1').
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 was vulnerable but has been fixed (note: '5.0.0-1025.26~18.04.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 was vulnerable but has been fixed (note: '4.15.0-1048.51').
OR
linux-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.26~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 was vulnerable but has been fixed (note: '5.0.0-35.38~18.04.1').
OR
linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1050.50').
OR
linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-69.78').
OR
linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1054.56').
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 was vulnerable but has been fixed (note: '5.0.0-1025.27~18.04.1').
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 was vulnerable but has been fixed (note: '5.0.0-1025.26~18.04.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 was vulnerable but has been fixed (note: '4.15.0-1048.51').
OR
linux-meta-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.26~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 was vulnerable but has been fixed (note: '5.0.0-35.38~18.04.1').
OR
linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1050.50').
OR
linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1063.72').
OR
linux-meta-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1027.31').
OR
linux-meta-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.32').
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 was vulnerable but has been fixed (note: '4.15.0-1050.54').
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 was vulnerable but has been fixed (note: '4.15.0-1067.74').
OR
linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1063.72').
OR
linux-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1027.31').
OR
linux-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.32').
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 was vulnerable but has been fixed (note: '4.15.0-1050.54').
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 was vulnerable but has been fixed (note: '4.15.0-69.78').
OR
linux-signed-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.27~18.04.1').
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 was vulnerable but has been fixed (note: '5.0.0-1025.26~18.04.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 was vulnerable but has been fixed (note: '4.15.0-1048.51').
OR
linux-signed-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.26~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 was vulnerable but has been fixed (note: '5.0.0-35.38~18.04.1').
OR
linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1063.72').
OR
linux-signed-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1027.31').
OR
linux-signed-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.32').
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 was vulnerable but has been fixed (note: '4.15.0-1067.74').
BACK