# CVE-2018-5997: File upload in n/a

> Attackers can upload malicious files via unrestricted upload and path traversal to execute code with root privileges on RAVPower Filehub devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 25 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w6wj-grq4-hrgj

## What is CVE-2018-5997?

CVE-2018-5997 is a critical vulnerability in n/a, published on 25 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the HTTP Server in RAVPower Filehub 2.000.056. Due to an unrestricted upload feature and a path traversal vulnerability, it is possible to upload a file on a filesystem with root privileges: this will lead to remote code execution as root.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2018-5997?

It affects 1 product.


Products: Ravpower Filehub Firmware.

## How do I fix CVE-2018-5997?

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

## Is CVE-2018-5997 being exploited?

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

Public exploit code:

- RAVPower 2.000.056 - Root Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-5319](https://insights.sbomify.com/CVE-2018-5319/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5997 and fix it if it is affected.

What it is: CVE-2018-5997 is a critical vulnerability in n/a, published on 25 Jan 2018. 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-2018-5997 in the wild and no public exploit code.

Affected product: n/a. 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-2018-5997/ (Markdown: https://insights.sbomify.com/CVE-2018-5997/index.md)
```

## Sources

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

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