Revision Date: | 2019-01-03 | Version: | 1 | Title: | CVE-2019-3701 on Ubuntu 19.04 (disco) - negligible. | Description: | An issue was discovered in can_can_gw_rcv in net/can/gw.c in the Linux kernel through 4.19.13. The CAN frame modification rules allow bitwise logical operations that can be also applied to the can_dlc field. The privileged user "root" with CAP_NET_ADMIN can create a CAN frame modification rule that makes the data length code a higher value than the available CAN frame data size. In combination with a configured checksum calculation where the result is stored relatively to the end of the data (e.g. cgw_csum_xor_rel) the tail of the skb (e.g. frag_list pointer in skb_shared_info) can be rewritten which finally can cause a system crash. Because of a missing check, the CAN drivers may write arbitrary content beyond the data registers in the CAN controller's I/O memory when processing can-gw manipulated outgoing frames. Muyu Yu discovered that the CAN implementation in the Linux kernel in some situations did not properly restrict the field size when processing outgoing frames. A local attacker with CAP_NET_ADMIN privileges could use this to execute arbitrary code.
| Family: | unix | Class: | vulnerability | Status: | | Reference(s): | CVE-2019-3701
| 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.19.0-12.13').
OR linux-aws package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-azure package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-gcp package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-kvm package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-meta package in disco, is related to the CVE in some way and has been fixed (note: '4.19.0-12.13').
OR linux-meta-aws package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-meta-azure package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-meta-gcp package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-meta-kvm package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-meta-oem package in disco is affected. An update containing the fix has been completed and is pending publication (note: '4.15.0-1056.65').
OR linux-meta-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-meta-oracle package in disco was vulnerable but has been fixed (note: '5.0.0-1004.8').
OR linux-meta-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1004.4').
OR linux-oem package in disco is affected. An update containing the fix has been completed and is pending publication (note: '4.15.0-1056.65').
OR linux-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-oracle package in disco was vulnerable but has been fixed (note: '5.0.0-1004.8').
OR linux-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1004.4').
OR linux-signed package in disco, is related to the CVE in some way and has been fixed (note: '4.19.0-12.13').
OR linux-signed-azure package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-signed-gcp package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1001.1').
OR linux-signed-oem package in disco is affected. An update containing the fix has been completed and is pending publication (note: '4.15.0-1056.65').
OR linux-signed-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-signed-oracle package in disco was vulnerable but has been fixed (note: '5.0.0-1004.8').
OR linux-snapdragon package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.10').
|
|