CVE-2020-7211

tftp.c in libslirp 4.1.0, as used in QEMU 4.2.0, does not prevent ..\ directory traversal on Windows.

Published: 2020-01-21 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-7211 is rated Moderate Risk (48.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.30%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-7211

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-30 0.46% 0.30% -0.16%
2 2025-03-30 1.15% 0.46% -0.69%
3 2025-03-29 — 1.15% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-7211

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2020-7211

OS Trackers for CVE-2020-7211

vendor priority summary link
debian unimportant CVE-2020-7211 unimportant priority: Debian including 1 source packages (libslirp), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2020-7211
redhat low — https://access.redhat.com/security/cve/CVE-2020-7211
suse medium CVE-2020-7211 severity moderate: SUSE including 65 source package names (xen, xen-4.0.3_21548_20-53.24.1, …), 173 product×package rows across 34 product lines (HPE Helion OpenStack 8, Image SLES12-SP5-EC2-BYOS, … (34 product lines)): Fixed 167, Known Not Affected 6. https://www.suse.com/security/cve/CVE-2020-7211/
ubuntu medium CVE-2020-7211 medium priority: Ubuntu including 3 source packages (libslirp, qemu, qemu-kvm), 18 status rows across 6 suites (bionic, disco, eoan, trusty, upstream, xenial): DNE 10, not-affected 4, needs-triage 3, ignored 1. https://ubuntu.com/security/CVE-2020-7211

Affected software / configurations for CVE-2020-7211

Vendor Product Version Raw CPE
libslirp_project libslirp 4.1.0 cpe:2.3:a:libslirp_project:libslirp:4.1.0:*:*:*:*:*:*:*
qemu qemu 4.2.0 cpe:2.3:a:qemu:qemu:4.2.0:*:*:*:*:*:*:*

References for CVE-2020-7211

cvelogic Threat Intelligence