CVE-2019-6778: Buffer Overflow
A heap buffer overflow issue was found in the SLiRP networking implementation of the QEMU emulator. It occurs in tcpemu() routine while emulating Identification protocol and copying message data to a socket buffer.
A user/process could use this flaw to crash the Qemu process on the host resulting in DoS or potentially execute arbitrary code with privileges of the QEMU process.
Upstream patch: --------------- -> https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg03132.html
Reference: ---------- -> https://www.openwall.com/lists/oss-security/2019/01/24/5
Other sources
A heap buffer overflow issue was found in the SLiRP networking implementation of the QEMU emulator. It occurs in tcpemu() routine while emulating the Identification protocol and copying message data to a socket buffer. A user or process could use this flaw to crash the QEMU process on the host resulting in a DoS or potentially executing arbitrary code with privileges of the QEMU process.
In QEMU 3.0.0, tcpemu in slirp/tcpsubr.c has a heap-based buffer overflow.
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-2019-6778?
CVE-2019-6778 has been rated as critical due to the potential for a heap buffer overflow leading to a crash of the QEMU process.
How do I fix CVE-2019-6778?
To mitigate CVE-2019-6778, upgrade QEMU to versions 2:0.12.1.2-2.506.el6_10.5 or higher for RHEL systems or the specific patched versions for Debian and Ubuntu as stated in the vulnerability advisory.
What systems are affected by CVE-2019-6778?
CVE-2019-6778 affects various versions of QEMU and QEMU KVM across multiple distributions including Red Hat, Debian, and Ubuntu.
What could happen if CVE-2019-6778 is exploited?
Exploitation of CVE-2019-6778 could allow an attacker to crash the QEMU process, leading to service disruption on the host.
Is there a workaround for CVE-2019-6778?
There is no official workaround for CVE-2019-6778; the only solution is to upgrade to a fixed version of QEMU.