# CVE-2021-20651: Path traversal in ELECOM File Manager

> Remote attackers can create or overwrite arbitrary files via directory traversal in ELECOM File Manager, potentially compromising data integrity.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-85c9-6xqv-2xcj

## What is CVE-2021-20651?

CVE-2021-20651 is a critical path traversal vulnerability in ELECOM File Manager, published on 12 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in ELECOM File Manager all versions allows remote attackers to create an arbitrary file or overwrite an existing file in a directory which can be accessed with the application privileges via unspecified vectors.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-20651?

It affects 1 product.


Products: Elecom File Manager.

## How do I fix CVE-2021-20651?

No fix has been published for CVE-2021-20651 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-20651 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-20651 and fix it if it is affected.

What it is: CVE-2021-20651 is a critical path traversal vulnerability in ELECOM File Manager, published on 12 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-20651 in the wild and no public exploit code.

Affected product: ELECOM File Manager. 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-2021-20651/ (Markdown: https://insights.sbomify.com/CVE-2021-20651/index.md)
```

## Sources

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

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