CVE-2020-7039
published 2020-01-16CVE-2020-7039: tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based…
PriorityP338medium5.6CVSS 3.1
AVNACHPRNUINSUCLILAL
EPSS
3.57%
88.1th percentile
tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code.
Affected
27 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | libslirp | < libslirp 4.1.0-2 (bookworm) | libslirp 4.1.0-2 (bookworm) |
| debian | qemu | < libslirp 4.1.0-2 (bookworm) | libslirp 4.1.0-2 (bookworm) |
| debian | slirp | < libslirp 4.1.0-2 (bookworm) | libslirp 4.1.0-2 (bookworm) |
| libslirp_project | libslirp | — | — |
| libslirp_project | libslirp | >= 0 < 4.1.0-2 | 4.1.0-2 |
| libslirp_project | libslirp | >= 0 < 4.1.0-2 | 4.1.0-2 |
| libslirp_project | libslirp | >= 0 < 4.1.0-2 | 4.1.0-2 |
| libslirp_project | libslirp | >= 0 < 4.1.0-2 | 4.1.0-2 |
| msrc | cbl_mariner_1.0_arm | — | — |
| msrc | cbl_mariner_1.0_x64 | — | — |
| msrc | cm1_qemu-kvm_4.2.0-13_on_cbl_mariner_1.0 | — | — |
| opensuse | leap | — | — |
| qemu | qemu | — | — |
| qemu | qemu | >= 0 < 1:4.1-2 | 1:4.1-2 |
| qemu | qemu | >= 0 < 1:4.1-2 | 1:4.1-2 |
| qemu | qemu | >= 0 < 1:4.1-2 | 1:4.1-2 |
| qemu | qemu | >= 0 < 1:4.1-2 | 1:4.1-2 |
| qemu | qemu | >= 0 < 1:2.5+dfsg-5ubuntu10.43 | 1:2.5+dfsg-5ubuntu10.43 |
| qemu | qemu | >= 0 < 1:2.11+dfsg-1ubuntu7.23 | 1:2.11+dfsg-1ubuntu7.23 |
| qemu | qemu | >= 0 < 1:4.2-3ubuntu6.30 | 1:4.2-3ubuntu6.30 |
| qemu | qemu | >= 0 < 1:6.2+dfsg-2ubuntu6.24 | 1:6.2+dfsg-2ubuntu6.24 |
| qemu | qemu | >= 0 < 1:8.2.2+ds-0ubuntu1.4 | 1:8.2.2+ds-0ubuntu1.4 |
| qemu | qemu | >= 0 < 2.0.0+dfsg-2ubuntu1.47+esm4 | 2.0.0+dfsg-2ubuntu1.47+esm4 |
CVSS provenance
nvdv3.15.6MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv6.0MEDIUM
vendor_ubuntu7.7HIGH
vendor_debian5.6MEDIUM
vendor_msrc5.6MEDIUM
vendor_redhat5.6MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
qemu vulnerabilities
osv·2024-11-08·CVSS 3.5
CVE-2019-20382 [LOW] qemu vulnerabilities
qemu vulnerabilities
It was discovered that QEMU incorrectly handled memory during certain VNC
operations. A remote attacker could possibly use this issue to cause QEMU
to consume resources, resulting in a denial of service. This issue only
affected Ubuntu 14.04 LTS. (CVE-2019-20382)
It was discovered that QEMU incorrectly handled certain memory copy
operations when loading ROM contents. If a user were tricked into running
an untrusted kernel image, a remote attacker could possibly use this issue
to run arbitrary code. This issue only affected Ubuntu 14.04 LTS.
(CVE-2020-13765)
Aviv Sasson discovered that QEMU incorrectly handled Slirp networking. A
remote attacker could use this issue to cause QEMU to crash, resulting in a
denial of service, or possibly execute arbitrary code. This iss
GHSA
GHSA-fr8m-vw66-8v9r: tcp_emu in tcp_subr
ghsa_unreviewed·2022-05-24
CVE-2020-7039 [HIGH] CWE-787 GHSA-fr8m-vw66-8v9r: tcp_emu in tcp_subr
tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code.
OSV
slirp vulnerabilities
osv·2020-11-12·CVSS 5.6
CVE-2020-7039 [MEDIUM] slirp vulnerabilities
slirp vulnerabilities
It was discovered that the SLiRP networking implementation of the QEMU
emulator did not properly manage memory under certain circumstances. An
attacker could use this to cause a heap-based buffer overflow or other out-
of-bounds access, which can lead to a denial of service (application crash)
or potentially execute arbitrary code. (CVE-2020-7039)
It was discovered that the SLiRP networking implementation of the QEMU
emulator misuses snprintf return values. An attacker could use this to
cause a denial of service (application crash) or potentially execute
arbitrary code. (CVE-2020-8608)
OSV
qemu vulnerabilities
osv·2020-02-18·CVSS 6.0
CVE-2020-1711 [MEDIUM] qemu vulnerabilities
qemu vulnerabilities
Felipe Franciosi, Raphael Norwitz, and Peter Turschmid discovered that QEMU
incorrectly handled iSCSI server responses. A remote attacker in control of
the iSCSI server could use this issue to cause QEMU to crash, leading to a
denial of service, or possibly execute arbitrary code. (CVE-2020-1711)
It was discovered that the QEMU libslirp component incorrectly handled
memory. A remote attacker could use this issue to cause QEMU to crash,
resulting in a denial of service, or possibly execute arbitrary code.
(CVE-2020-7039, CVE-2020-8608)
OSV
CVE-2020-7039: tcp_emu in tcp_subr
osv·2020-01-16·CVSS 5.6
CVE-2020-7039 [MEDIUM] CVE-2020-7039: tcp_emu in tcp_subr
tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code.
Ubuntu
QEMU vulnerabilities
vendor_ubuntu·2024-11-08·CVSS 3.5
CVE-2020-8608 [LOW] QEMU vulnerabilities
Title: QEMU vulnerabilities
Summary: Several security issues were fixed in QEMU.
It was discovered that QEMU incorrectly handled memory during certain VNC
operations. A remote attacker could possibly use this issue to cause QEMU
to consume resources, resulting in a denial of service. This issue only
affected Ubuntu 14.04 LTS. (CVE-2019-20382)
It was discovered that QEMU incorrectly handled certain memory copy
operations when loading ROM contents. If a user were tricked into running
an untrusted kernel image, a remote attacker could possibly use this issue
to run arbitrary code. This issue only affected Ubuntu 14.04 LTS.
(CVE-2020-13765)
Aviv Sasson discovered that QEMU incorrectly handled Slirp networking. A
remote attacker could use this issue to cause QEMU to crash, resulting in a
de
Ubuntu
SLiRP vulnerabilities
vendor_ubuntu·2020-11-12·CVSS 5.6
CVE-2020-7039 [MEDIUM] SLiRP vulnerabilities
Title: SLiRP vulnerabilities
Summary: slirp could be made to crash if it received specially crafted
input.
It was discovered that the SLiRP networking implementation of the QEMU
emulator did not properly manage memory under certain circumstances. An
attacker could use this to cause a heap-based buffer overflow or other out-
of-bounds access, which can lead to a denial of service (application crash)
or potentially execute arbitrary code. (CVE-2020-7039)
It was discovered that the SLiRP networking implementation of the QEMU
emulator misuses snprintf return values. An attacker could use this to
cause a denial of service (application crash) or potentially execute
arbitrary code. (CVE-2020-8608)
Instructions: In general, a standard system update will make all the necessary changes.
Ubuntu
QEMU vulnerabilities
vendor_ubuntu·2020-02-18·CVSS 7.7
CVE-2020-1711 [HIGH] QEMU vulnerabilities
Title: QEMU vulnerabilities
Summary: Several security issues were fixed in QEMU.
Felipe Franciosi, Raphael Norwitz, and Peter Turschmid discovered that QEMU
incorrectly handled iSCSI server responses. A remote attacker in control of
the iSCSI server could use this issue to cause QEMU to crash, leading to a
denial of service, or possibly execute arbitrary code. (CVE-2020-1711)
It was discovered that the QEMU libslirp component incorrectly handled
memory. A remote attacker could use this issue to cause QEMU to crash,
resulting in a denial of service, or possibly execute arbitrary code.
(CVE-2020-7039, CVE-2020-8608)
Instructions: After a standard system update you need to restart all QEMU virtual
machines to make all the necessary changes.
Microsoft
tcp_emu in tcp_subr.c in libslirp 4.1.0 as used in QEMU 4.2.0 mismanages memory as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds acces
vendor_msrc·2020-01-14·CVSS 5.6
CVE-2020-7039 [MEDIUM] CWE-787 tcp_emu in tcp_subr.c in libslirp 4.1.0 as used in QEMU 4.2.0 mismanages memory as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds acces
tcp_emu in tcp_subr.c in libslirp 4.1.0 as used in QEMU 4.2.0 mismanages memory as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If i
Red Hat
QEMU: slirp: OOB buffer access while emulating tcp protocols in tcp_emu()
vendor_redhat·2020-01-07·CVSS 5.6
CVE-2020-7039 [MEDIUM] CWE-122 QEMU: slirp: OOB buffer access while emulating tcp protocols in tcp_emu()
QEMU: slirp: OOB buffer access while emulating tcp protocols in tcp_emu()
tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code.
A heap buffer overflow issue was found in the SLiRP networking implementation of the QEMU emulator. This flaw occurs in the tcp_emu() routine while emulating IRC and other protocols. An attacker could use this flaw to crash the QEMU process on the host, resulting in a denial of service or potential execution of arbitrary code with privileges of the QEMU process.
Statement: This issue affects user-mode or SLiRP networking implementation of the QEMU emula
Debian
CVE-2020-7039: libslirp - tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memor...
vendor_debian·2020·CVSS 5.6
CVE-2020-7039 [MEDIUM] CVE-2020-7039: libslirp - tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memor...
tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code.
Scope: local
bookworm: resolved (fixed in 4.1.0-2)
bullseye: resolved (fixed in 4.1.0-2)
forky: resolved (fixed in 4.1.0-2)
sid: resolved (fixed in 4.1.0-2)
trixie: resolved (fixed in 4.1.0-2)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-7039 QEMU: slirp: OOB buffer access while emulating tcp protocols in tcp_emu()
bugzilla·2020-01-16·CVSS 5.6
CVE-2020-7039 [MEDIUM] CVE-2020-7039 QEMU: slirp: OOB buffer access while emulating tcp protocols in tcp_emu()
CVE-2020-7039 QEMU: slirp: OOB buffer access while emulating tcp protocols in tcp_emu()
A heap buffer overflow issue was found in the SLiRP networking implementation
of the QEMU emulator. It occurs in tcp_emu() routine while emulating IRC and
other protocols.
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(es):
-> https://gitlab.freedesktop.org/slirp/libslirp/commit/2655fffed7a9e765bcb4701dd876e9dab975f289
-> https://gitlab.freedesktop.org/slirp/libslirp/commit/ce131029d6d4a405cb7d3ac6716d03e58fb4a5d9
-> https://gitlab.freedesktop.org/slirp/libslirp/commit/82ebe9c370a0e2970fb5695aa19aa5214a6a1c80
Reference:
-> https://www.openwall.com/lists/oss-security/20
Bugzilla
CVE-2020-7039 qemu: slirp: OOB buffer access while emulating tcp protocols in tcp_emu() [fedora-all]
bugzilla·2020-01-16·CVSS 5.6
CVE-2020-7039 [MEDIUM] CVE-2020-7039 qemu: slirp: OOB buffer access while emulating tcp protocols in tcp_emu() [fedora-all]
CVE-2020-7039 qemu: slirp: OOB buffer access while emulating tcp protocols in tcp_emu() [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects mult
Unit42
Rootless Containers: The Next Trend in Container Security
blogs_unit42·2020-05-26
Rootless Containers: The Next Trend in Container Security
Threat Research Center
Threat Research
Cloud Cybersecurity Research
## Rootless Containers: The Next Trend in Container Security
Aviv Sasson
Published: May 26, 2020
Cloud Cybersecurity Research
Threat Research
Podman LXC Container Security
Rootless Containers
Slirp
## Executive Summary
As cloud computing evolves, containers continue to become more and more popular. New solutions and ideas to the way we implement containers are being introduced. One of these new ideas is rootless containers.
Rootless containers is a new concept of containers that don’t require root privileges in order to formulate. Many solutions have been proposed to overcome the technological challenges of creating a container with an unprivileged user, some of them are still under development and some ar
Unit42
Rootless Containers: The Next Trend in Container Security
blogs_unit42·2020-05-26
Rootless Containers: The Next Trend in Container Security
## Executive Summary
As cloud computing evolves, containers continue to become more and more popular. New solutions and ideas to the way we implement containers are being introduced. One of these new ideas is rootless containers.
Rootless containers is a new concept of containers that don’t require root privileges in order to formulate. Many solutions have been proposed to overcome the technological challenges of creating a container with an unprivileged user, some of them are still under development and some are production-ready. While rootless containers present some advantages, mainly from a security perspective, they are still in their early stages.
In this post, Unit 42 researcher Aviv Sasson reviews the internals of rootless containers. Aviv also presents a vulnerability he found
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00007.htmlhttp://www.openwall.com/lists/oss-security/2020/01/16/2https://access.redhat.com/errata/RHSA-2020:0348https://access.redhat.com/errata/RHSA-2020:0775https://gitlab.freedesktop.org/slirp/libslirp/commit/2655fffed7a9e765bcb4701dd876e9dab975f289https://gitlab.freedesktop.org/slirp/libslirp/commit/82ebe9c370a0e2970fb5695aa19aa5214a6a1c80https://gitlab.freedesktop.org/slirp/libslirp/commit/ce131029d6d4a405cb7d3ac6716d03e58fb4a5d9https://lists.debian.org/debian-lts-announce/2020/01/msg00022.htmlhttps://lists.debian.org/debian-lts-announce/2020/01/msg00036.htmlhttps://lists.debian.org/debian-lts-announce/2021/02/msg00012.htmlhttps://seclists.org/bugtraq/2020/Feb/0https://security.gentoo.org/glsa/202005-02https://usn.ubuntu.com/4283-1/https://www.debian.org/security/2020/dsa-4616http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00007.htmlhttp://www.openwall.com/lists/oss-security/2020/01/16/2https://access.redhat.com/errata/RHSA-2020:0348https://access.redhat.com/errata/RHSA-2020:0775https://gitlab.freedesktop.org/slirp/libslirp/commit/2655fffed7a9e765bcb4701dd876e9dab975f289https://gitlab.freedesktop.org/slirp/libslirp/commit/82ebe9c370a0e2970fb5695aa19aa5214a6a1c80https://gitlab.freedesktop.org/slirp/libslirp/commit/ce131029d6d4a405cb7d3ac6716d03e58fb4a5d9https://lists.debian.org/debian-lts-announce/2020/01/msg00022.htmlhttps://lists.debian.org/debian-lts-announce/2020/01/msg00036.htmlhttps://lists.debian.org/debian-lts-announce/2021/02/msg00012.htmlhttps://seclists.org/bugtraq/2020/Feb/0https://security.gentoo.org/glsa/202005-02https://usn.ubuntu.com/4283-1/https://www.debian.org/security/2020/dsa-4616
2020-01-16
Published