CVE-2020-6105

Exp

An exploitable code execution vulnerability exists in the multiple devices functionality of F2fs-Tools F2fs.Fsck 1.13. A specially crafted f2fs filesystem can cause Information overwrite resulting in a code execution. An attacker can provide a malicious file to trigger this vulnerability.

Published: 2020-10-15 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-6105 is rated High Exploit Risk (75/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.01%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +1.42% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2020-6105

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

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

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 2026-06-15 0.59% 2.01% +1.42%
2 2025-03-30 1.71% 0.59% -1.12%
3 2025-03-29 — 1.71% —

Full EPSS history (10 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
8.2 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.5 6.0 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2020-6105

OS Trackers for CVE-2020-6105

vendor priority summary link
alpine high CVE-2020-6105: 1 source package rows (f2fs-tools); 8 state rows across 8 repos (3.10-main, 3.11-main, 3.12-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 5, open 3. https://security.alpinelinux.org/vuln/CVE-2020-6105
debian not yet assigned CVE-2020-6105 not yet assigned priority: Debian including 1 source packages (f2fs-tools), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-6105
gentoo normal CVE-2020-6105: 1 GLSA(s) (202101-26), 1 atom(s) (sys-fs/f2fs-tools); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-6105
ubuntu medium CVE-2020-6105 medium priority: Ubuntu including 1 source packages (f2fs-tools), 16 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 8, needs-triage 7, DNE 1. https://ubuntu.com/security/CVE-2020-6105

Affected software / configurations for CVE-2020-6105

Vendor Product Version Raw CPE
f2fs-tools_project f2fs-tools < 1.14.0 cpe:2.3:a:f2fs-tools_project:f2fs-tools:*:*:*:*:*:*:*:*

References for CVE-2020-6105

URL Tags
https://security.gentoo.org/glsa/202101-26 Third Party Advisory
https://talosintelligence.com/vulnerability_reports/TALOS-2020-1047 Exploit Technical Description Third Party Advisory
cvelogic Threat Intelligence