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

> An attacker can exploit a path traversal vulnerability in tele_compress.php to read arbitrary files from the OSSIM server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 27 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8j5m-mpjv-6g62

## What is CVE-2013-6056?

CVE-2013-6056 is a high-severity path traversal vulnerability in n/a, published on 27 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OSSIM before 4.3.3.1 has tele_compress.php path traversal vulnerability

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

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

It affects 1 product.


Products: Alienvault Open Source Security Information Management.

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

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

## Is CVE-2013-6056 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5158](https://insights.sbomify.com/CVE-2014-5158/): Command injection in n/a (critical 10.0)
- [CVE-2014-5210](https://insights.sbomify.com/CVE-2014-5210/): Command injection in n/a (critical 10.0)
- [CVE-2014-4151](https://insights.sbomify.com/CVE-2014-4151/): Code injection in n/a (critical 10.0)
- [CVE-2014-4152](https://insights.sbomify.com/CVE-2014-4152/): Code injection in n/a (critical 10.0)
- [CVE-2014-3804](https://insights.sbomify.com/CVE-2014-3804/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6056 is a high-severity path traversal vulnerability in n/a, published on 27 Jan 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-2013-6056 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-6056/ (Markdown: https://insights.sbomify.com/CVE-2013-6056/index.md)
```

## Sources

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

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