# CVE-2020-6106: Information disclosure in F2fs-Tools

> An attacker can disclose information by providing a specially crafted filesystem to the F2fs-Tools fsck utility.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2020-6106, DEBIAN-CVE-2020-6106, GHSA-g2pw-hx42-qrf8, UBUNTU-CVE-2020-6106

## What is CVE-2020-6106?

CVE-2020-6106 is a medium-severity vulnerability in F2fs-Tools, published on 15 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An exploitable information disclosure vulnerability exists in the init_node_manager functionality of F2fs-Tools F2fs.Fsck 1.12 and 1.13. A specially crafted filesystem can be used to disclose information. An attacker can provide a malicious file to trigger this vulnerability.

Weakness: CWE-125 (Out-of-bounds Read), CWE-131 (Incorrect Calculation of Buffer Size)

## Which versions are affected by CVE-2020-6106?

It affects 1 product.


Products: F2fs-Tools Project F2fs-Tools.

## How do I fix CVE-2020-6106?

Apply the vendor's patch.

## Is CVE-2020-6106 being exploited?

There is no known exploitation of CVE-2020-6106 in the wild and no public exploit code.

## Other vulnerabilities in F2fs-Tools

- [CVE-2020-6105](https://insights.sbomify.com/CVE-2020-6105/): Code injection in F2fs-Tools (high 8.2)
- [CVE-2020-6108](https://insights.sbomify.com/CVE-2020-6108/): Memory corruption in F2fs-Tools (high 8.2)
- [CVE-2020-6070](https://insights.sbomify.com/CVE-2020-6070/): Memory corruption in F2fs-tools (medium 6.7)
- [CVE-2020-6104](https://insights.sbomify.com/CVE-2020-6104/): Information disclosure in F2FS-Tools (medium 4.4)
- [CVE-2020-6107](https://insights.sbomify.com/CVE-2020-6107/): Information disclosure in F2fs-Tools (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6106 and fix it if it is affected.

What it is: CVE-2020-6106 is a medium-severity vulnerability in F2fs-Tools, published on 15 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6106 in the wild and no public exploit code.

Affected product: F2fs-Tools. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-6106/ (Markdown: https://insights.sbomify.com/CVE-2020-6106/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-6106
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-6106
- OSV: https://osv.dev/vulnerability/CVE-2020-6106

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-6106/
Summaries are generated and may contain mistakes; the official description above is the record.