CVE-2020-7039

Description

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.

Category

5.6
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 1.02% Top 25%
Vendor Advisory debian.org Vendor Advisory redhat.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory opensuse.org Vendor Advisory gentoo.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://gitlab.freedesktop.org/slirp/libslirp/commit/ce131029d6d4a405cb7d3ac6716d03e58fb4a5d9 third party advisory patch
https://gitlab.freedesktop.org/slirp/libslirp/commit/82ebe9c370a0e2970fb5695aa19aa5214a6a1c80 third party advisory patch
https://gitlab.freedesktop.org/slirp/libslirp/commit/2655fffed7a9e765bcb4701dd876e9dab975f289 third party advisory patch
http://www.openwall.com/lists/oss-security/2020/01/16/2 mailing list third party advisory patch
https://lists.debian.org/debian-lts-announce/2020/01/msg00022.html third party advisory mailing list
https://lists.debian.org/debian-lts-announce/2020/01/msg00036.html third party advisory mailing list
https://seclists.org/bugtraq/2020/Feb/0 third party advisory mailing list
https://www.debian.org/security/2020/dsa-4616 third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2020:0348 third party advisory vendor advisory
https://usn.ubuntu.com/4283-1/ third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2020:0775 third party advisory vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00007.html third party advisory vendor advisory
https://security.gentoo.org/glsa/202005-02 third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2021/02/msg00012.html third party advisory mailing list

Frequently Asked Questions

What is the severity of CVE-2020-7039?
CVE-2020-7039 has been scored as a medium severity vulnerability.
How to fix CVE-2020-7039?
To fix CVE-2020-7039, 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-2020-7039 being actively exploited in the wild?
It is possible that CVE-2020-7039 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.