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

> Authenticated remote attackers can read arbitrary files via crafted URLs in IBM Optim Performance Manager.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/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:** 22 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r9wr-qv2x-hhw9

## What is CVE-2013-2979?

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

### Official description

Directory traversal vulnerability in IBM Optim Performance Manager 4.1.1 and IBM InfoSphere Optim Performance Manager 5.x before 5.2 allows remote authenticated users to read arbitrary files via a crafted URL.

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

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

It affects 2 products.


Products: Ibm Infosphere Optim Performance Manager, Ibm Optim Performance Manager.

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

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

## Is CVE-2013-2979 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2979 is a medium-severity path traversal vulnerability in n/a, published on 22 Aug 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2979 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-2979/ (Markdown: https://insights.sbomify.com/CVE-2013-2979/index.md)
```

## Sources

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

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