CVE-2020-27617: Medium severity qemu vulnerability
An assert(3) failure flaw was found in the networking helper functions of QEMU. This vulnerability can occur in the ethgetgsotype() routine if a packet does not have a valid networking L3 protocol (ex. IPv4, IPv6) value. This flaw allows a guest user to crash the QEMU process on the host, resulting in a denial of service.
Other sources
An assert(3) failure issue was found in the networking helper functions of QEMU. It could occur in the ethgetgsotype() routine, if a packet does not have a valid networking L3 protocol (ex. IPv4, IPv6) value. A guest user may use this flaw to crash the QEMU process on the host resulting in DoS scenario.
Upstream patch: --------------- -> https://lists.nongnu.org/archive/html/qemu-devel/2020-10/msg06023.html
— Red Hat
ethgetgsotype in net/eth.c in QEMU 4.2.1 allows guest OS users to trigger an assertion failure. A guest can crash the QEMU process via packet data that lacks a valid Layer 3 protocol.
Affected Software
Remediation
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2020-27617?
CVE-2020-27617 has a medium severity rating which indicates it could effectively lead to a denial of service.
How do I fix CVE-2020-27617?
To fix CVE-2020-27617, update QEMU to version 5.2.0 or higher if you are using Red Hat, or to specific patched versions if you are using Debian.
What systems are affected by CVE-2020-27617?
CVE-2020-27617 affects various versions of QEMU and Debian Linux, specifically the versions mentioned in the vulnerability details.
What kind of attack is possible with CVE-2020-27617?
An attacker can exploit CVE-2020-27617 by sending invalid network packets, potentially crashing the QEMU process on the host.
Is CVE-2020-27617 exploitable remotely?
Yes, CVE-2020-27617 can be exploited remotely if an attacker has access to the networking services of a vulnerable QEMU instance.