CVE-2019-13164

Description

qemu-bridge-helper.c in QEMU 3.1 and 4.0.0 does not ensure that a network interface name (obtained from bridge.conf or a --br=bridge option) is limited to the IFNAMSIZ size, which can lead to an ACL bypass.

7.8

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.07%

Vendor Advisory debian.org Vendor Advisory opensuse.org Vendor Advisory debian.org Vendor Advisory opensuse.org Vendor Advisory ubuntu.com Vendor Advisory ubuntu.com Vendor Advisory gentoo.org Vendor Advisory gnu.org

Affected: n/a n/a

References

Link	Tags
https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg00145.html	mailing list patch vendor advisory
http://www.openwall.com/lists/oss-security/2019/07/02/2	third party advisory mailing list
http://www.securityfocus.com/bid/109054	vdb entry broken link
https://seclists.org/bugtraq/2019/Aug/41	third party advisory mailing list
https://www.debian.org/security/2019/dsa-4506	third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00000.html	mailing list third party advisory vendor advisory
https://www.debian.org/security/2019/dsa-4512	third party advisory vendor advisory
https://seclists.org/bugtraq/2019/Sep/3	third party advisory mailing list
http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00008.html	mailing list third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2019/09/msg00021.html	third party advisory mailing list
https://usn.ubuntu.com/4191-2/	third party advisory vendor advisory
https://usn.ubuntu.com/4191-1/	third party advisory vendor advisory
https://security.gentoo.org/glsa/202003-66	third party advisory vendor advisory
https://github.com/qemu/qemu/commit/03d7712b4bcd47bfe0fe14ba2fffa87e111fa086	third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2019-13164?: CVE-2019-13164 has been scored as a high severity vulnerability.
How to fix CVE-2019-13164?: To fix CVE-2019-13164, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-13164 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2019-13164 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.