BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2020
CVE-2020-7039High confidence

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

n/a · n/a

5.6MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2020-28173

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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.

What

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.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

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.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Out-of-bounds Write → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-787
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-3379QEMU: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in QEMU ausnutzen, um beliebigen Programmcode auszuführen, einen Denial of Service Angriff durchzuführen oder Informationen offenzulegen.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0997Multiples vulnérabilités dans le noyau Linux d'Ubuntu

ité Ubuntu USN-7088-5 du 14 novembre 2024 https://ubuntu.com/security/notices/USN-7088-5 Bulletin de sécurité Ubuntu USN-7089-5 du 14 novembre 2024 https://ubuntu.com/security/notices/USN-7089-5 Bulletin de sécurité Ubuntu USN-7110-1 du 14 novembre 2024 https://ubuntu.com/security/notices/USN-7110-1 Bulletin de sécurité Ubuntu USN-7089-6 du 15 novembre 2024 https://ubuntu.com/security/notices/USN-7089-6 Référence CVE CVE-2019-20382 https://www.cve.org/CVERecord?id=CVE-2019-20382 Référence CVE CVE-2020-13765 https://www.cve.org/CVERecord?id=CVE-2020-13765 Référence CVE CVE-2020-1983 https://www.cve.org/CVERecord?id=CVE-2020-1983 Référence CVE CVE-2020-7039 https://www.cve.org/CVERecord?id=CVE-2020-7039 Référence CVE CVE-2020-8608 https://www.cve.org/CVERecord?id=CVE-2020-8608 Référence CVE CVE-2021-3592 https://www.cve.org/CVERecord?id=CVE-2021-3592 Référence CVE CVE-2021-3594 https://www.cve.org/CVERecord?id=CVE-2021-3594 Référence CVE CVE-2021-47212 https://www.cve.org/CVERecord?id=CVE-2021-47212 Référence CVE CVE-2022-36402 https://www.cve.org/CVERecord?id=CVE-2022-36402 Référence CVE CVE-2022-48666 https://www.cve.org/CVERecord?id=CVE-2022-48666 Référence CVE CVE-2023-3019 https://www.cve.org/CVERecord?id=CVE-2023-3019 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-267Multiples vulnérabilités dans Juniper Networks Junos Space

/CVERecord?id=CVE-2020-1749 Référence CVE CVE-2020-1983 https://www.cve.org/CVERecord?id=CVE-2020-1983 Référence CVE CVE-2020-24394 https://www.cve.org/CVERecord?id=CVE-2020-24394 Référence CVE CVE-2020-25212 https://www.cve.org/CVERecord?id=CVE-2020-25212 Référence CVE CVE-2020-25637 https://www.cve.org/CVERecord?id=CVE-2020-25637 Référence CVE CVE-2020-25643 https://www.cve.org/CVERecord?id=CVE-2020-25643 Référence CVE CVE-2020-2732 https://www.cve.org/CVERecord?id=CVE-2020-2732 Référence CVE CVE-2020-5208 https://www.cve.org/CVERecord?id=CVE-2020-5208 Référence CVE CVE-2020-6829 https://www.cve.org/CVERecord?id=CVE-2020-6829 Référence CVE CVE-2020-7039 https://www.cve.org/CVERecord?id=CVE-2020-7039 Référence CVE CVE-2020-8647 https://www.cve.org/CVERecord?id=CVE-2020-8647 Référence CVE CVE-2020-8649 https://www.cve.org/CVERecord?id=CVE-2020-8649 Référence CVE CVE-2020-9383 https://www.cve.org/CVERecord?id=CVE-2020-9383 Référence CVE CVE-2021-3156 https://www.cve.org/CVERecord?id=CVE-2021-3156 Référence CVE CVE-2021-3396 https://www.cve.org/CVERecord?id=CVE-2021-3396 Gestion détaillée du document le 23 mars 2022 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
n/a: n/a
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 16 Jan 2020 · Last source change 4 Aug 2024, 09:18 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2020-28173
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2020-7039 · cve.blacktree.nl