# CVE-2013-6785: Path traversal in n/a

> Authenticated attackers can read arbitrary files on Supermicro IPMI devices via a directory traversal vulnerability in the url_redirect.cgi script.

- **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:** 23 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4gj7-vvp2-fcxc

## What is CVE-2013-6785?

CVE-2013-6785 is a medium-severity path traversal vulnerability in n/a, published on 23 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in url_redirect.cgi in Supermicro IPMI before SMT_X9_315 allows authenticated attackers to read arbitrary files via the url_name parameter.

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

## Which versions are affected by CVE-2013-6785?

It affects 1 product.


Products: Supermicro Intelligent Platform Management Interface.

## How do I fix CVE-2013-6785?

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

## Is CVE-2013-6785 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6785 exists.

Public exploit code:

- Supermicro Onboard IPMI url_redirect.cgi Authenticated Directory Traversal (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6785 and fix it if it is affected.

What it is: CVE-2013-6785 is a medium-severity path traversal vulnerability in n/a, published on 23 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6785 exists.

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-2013-6785/ (Markdown: https://insights.sbomify.com/CVE-2013-6785/index.md)
```

## Sources

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

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