# CVE-2020-5605: Path traversal in WHR-G54S

> An attacker can exploit a directory traversal flaw in Buffalo WHR-G54S routers to access sensitive configuration data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ch7q-2q5r-pf55

## What is CVE-2020-5605?

CVE-2020-5605 is a medium-severity path traversal vulnerability in BUFFALO INC. WHR-G54S, published on 18 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in WHR-G54S firmware 1.43 and earlier allows an attacker to access sensitive information such as setting values via unspecified vectors.

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

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

It affects 1 product.


Products: Buffalo Airstation Whr-G54s Firmware.

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

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

## Is CVE-2020-5605 being exploited?

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

## Other vulnerabilities in BUFFALO INC. WHR-G54S

- [CVE-2020-5606](https://insights.sbomify.com/CVE-2020-5606/): Cross-site scripting in WHR-G54S (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5605 is a medium-severity path traversal vulnerability in BUFFALO INC. WHR-G54S, published on 18 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-5605 in the wild and no public exploit code.

Affected product: BUFFALO INC. WHR-G54S. 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-5605/ (Markdown: https://insights.sbomify.com/CVE-2020-5605/index.md)
```

## Sources

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

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