First published: Mon Jan 27 2020(Updated: )
A out-of-bounds heap buffer access issue was found in the SLiRP networking implementation of the QEMU emulator. It occurs in tcp_emu() routine while emulating IRC and other protocols due to unsafe usage of snprintf(3) function. 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 on the host. Also with SELinux and sVirt access control in place, malicious activity is restricted. Upstream patch: --------------- -> <a href="https://gitlab.freedesktop.org/slirp/libslirp/commit/68ccb8021a838066f0951d4b2817eb6b6f10a843">https://gitlab.freedesktop.org/slirp/libslirp/commit/68ccb8021a838066f0951d4b2817eb6b6f10a843</a> -> <a href="https://gitlab.freedesktop.org/slirp/libslirp/commit/30648c03b27fb8d9611b723184216cd3174b6775">https://gitlab.freedesktop.org/slirp/libslirp/commit/30648c03b27fb8d9611b723184216cd3174b6775</a> Reference: ---------- -> <a href="https://www.openwall.com/lists/oss-security/2020/02/06/2">https://www.openwall.com/lists/oss-security/2020/02/06/2</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/qemu-kvm | <2:0.12.1.2-2.506.el6_10.7 | 2:0.12.1.2-2.506.el6_10.7 |
redhat/qemu-kvm | <10:1.5.3-173.el7_8.1 | 10:1.5.3-173.el7_8.1 |
redhat/qemu-kvm-ma | <10:2.12.0-44.el7_8.1 | 10:2.12.0-44.el7_8.1 |
redhat/qemu-kvm | <10:1.5.3-160.el7_6.7 | 10:1.5.3-160.el7_6.7 |
redhat/qemu-kvm | <10:1.5.3-167.el7_7.6 | 10:1.5.3-167.el7_7.6 |
redhat/qemu-kvm-ma | <10:2.12.0-33.el7_7.3 | 10:2.12.0-33.el7_7.3 |
redhat/slirp4netns | <0:0.3.0-8.el7_7 | 0:0.3.0-8.el7_7 |
redhat/atomic-enterprise-service-catalog | <1:4.3.3-202002170501.git.1.f30799e.el7 | 1:4.3.3-202002170501.git.1.f30799e.el7 |
redhat/atomic-openshift-service-idler | <0:4.3.3-202002170501.git.1.4feff9c.el7 | 0:4.3.3-202002170501.git.1.4feff9c.el7 |
redhat/cri-o | <0:1.16.3-20.dev.rhaos4.3.git11c04e3.el7 | 0:1.16.3-20.dev.rhaos4.3.git11c04e3.el7 |
redhat/cri-tools | <0:1.17.0-1.el8 | 0:1.17.0-1.el8 |
redhat/dracut | <0:049-64.git20200123.el8 | 0:049-64.git20200123.el8 |
redhat/jenkins | <0:2.204.1.1581950993-1.el7 | 0:2.204.1.1581950993-1.el7 |
redhat/jenkins | <2-plugins-0:4.3.1581956184-1.el7 | 2-plugins-0:4.3.1581956184-1.el7 |
redhat/machine-config-daemon | <0:4.3.3-202002170501.git.1.6b1b155.el8 | 0:4.3.3-202002170501.git.1.6b1b155.el8 |
redhat/openshift | <0:4.3.3-202002140552.git.0.e38059c.el7 | 0:4.3.3-202002140552.git.0.e38059c.el7 |
redhat/openshift-ansible | <0:4.3.3-202002142331.git.173.bb0b5a1.el7 | 0:4.3.3-202002142331.git.173.bb0b5a1.el7 |
redhat/openshift-clients | <0:4.3.3-202002140552.git.1.ff73b47.el7 | 0:4.3.3-202002140552.git.1.ff73b47.el7 |
redhat/openshift-kuryr | <0:4.3.3-202002170501.git.1.3b8b4cc.el8 | 0:4.3.3-202002170501.git.1.3b8b4cc.el8 |
redhat/slirp4netns | <0:0.4.2-4.git21fdece.el8 | 0:0.4.2-4.git21fdece.el8 |
redhat/toolbox | <0:0.0.6-1.rhaos4.3.el8 | 0:0.0.6-1.rhaos4.3.el8 |
redhat/qemu-kvm-rhev | <10:2.12.0-33.el7_7.10 | 10:2.12.0-33.el7_7.10 |
redhat/qemu-kvm-rhev | <10:2.12.0-44.el7_8.1 | 10:2.12.0-44.el7_8.1 |
redhat/qemu-kvm-rhev | <10:2.12.0-18.el7_6.11 | 10:2.12.0-18.el7_6.11 |
redhat/libslirp | <4.3.0 | 4.3.0 |
debian/libslirp | 4.4.0-1+deb11u2 4.7.0-1 4.8.0-1 | |
debian/qemu | 1:5.2+dfsg-11+deb11u3 1:5.2+dfsg-11+deb11u2 1:7.2+dfsg-7+deb12u12 1:9.2.1+ds-1 | |
debian/slirp | 1:1.0.17-11 | |
debian/slirp4netns | 1.0.1-2 1.2.0-1 1.2.1-1 | |
libslirp | =4.1.0 | |
Debian | =8.0 | |
Debian | =9.0 | |
Debian | =10.0 | |
SUSE Linux | =15.1 |
This issue can only be resolved by applying updates. Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2020-8608 is classified as a medium severity vulnerability due to its potential to crash the QEMU process.
To fix CVE-2020-8608, you need to upgrade to a patched version of the QEMU package specified in the security advisories.
CVE-2020-8608 affects the SLiRP networking implementation in various versions of QEMU and related packages.
Yes, CVE-2020-8608 can be exploited by an attacker who can send specially crafted data to the emulated network protocols.
Exploitation of CVE-2020-8608 could lead to a denial of service by crashing the QEMU process.