# CVE-2020-5554: Path traversal in Shihonkanri Plus GOOUT

> Remote attackers can read and write arbitrary files in Shihonkanri Plus GOOUT via a directory traversal vulnerability.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wffx-cv79-89x8

## What is CVE-2020-5554?

CVE-2020-5554 is a critical path traversal vulnerability in EKAKIN Shihonkanri Plus GOOUT, published on 25 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in Shihonkanri Plus GOOUT Ver1.5.8 and Ver2.2.10 allows remote attackers to read and write arbitrary files via unspecified vectors.

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

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

It affects 1 product.


Products: Shihonkanri Plus Goout Project Shihonkanri Plus Goout.

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

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

## Is CVE-2020-5554 being exploited?

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

## Other vulnerabilities in EKAKIN Shihonkanri Plus GOOUT

- [CVE-2020-5556](https://insights.sbomify.com/CVE-2020-5556/): Command injection in Shihonkanri Plus GOOUT (critical 9.8)
- [CVE-2020-5555](https://insights.sbomify.com/CVE-2020-5555/): Path traversal in Shihonkanri Plus GOOUT (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5554 is a critical path traversal vulnerability in EKAKIN Shihonkanri Plus GOOUT, published on 25 Mar 2020. 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-2020-5554 in the wild and no public exploit code.

Affected product: EKAKIN Shihonkanri Plus GOOUT. 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-5554/ (Markdown: https://insights.sbomify.com/CVE-2020-5554/index.md)
```

## Sources

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

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