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

> Remote attackers can read or write arbitrary files in SAP adminadapter via unspecified vectors, risking data exposure and integrity.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2rqf-hc6v-jrjp

## What is CVE-2013-7360?

CVE-2013-7360 is a high-severity path traversal vulnerability in n/a, published on 10 Apr 2014. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in SAP adminadapter allows remote attackers to read or write to arbitrary files via unknown vectors.

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

It affects 1 product.


Products: Sap Adminadapter.

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

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

## Is CVE-2013-7360 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7360 is a high-severity path traversal vulnerability in n/a, published on 10 Apr 2014. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-7360 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-2013-7360/ (Markdown: https://insights.sbomify.com/CVE-2013-7360/index.md)
```

## Sources

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

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