# CVE-2015-0550: Path traversal in n/a

> Remote attackers can bypass Content Server access restrictions via directory traversal in EMC Documentum Thumbnail Server.

- **Severity:** High 8.5 (`AV:N/AC:L/Au:N/C:C/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p637-6x4f-cmfc

## What is CVE-2015-0550?

CVE-2015-0550 is a high-severity path traversal vulnerability in n/a, published on 28 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in EMC Documentum Thumbnail Server 6.7SP1 before P32, 6.7SP2 before P25, 7.0 before P19, 7.1 before P16, and 7.2 before P01 allows remote attackers to bypass intended Content Server access restrictions via unspecified vectors.

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

## Which versions are affected by CVE-2015-0550?

It affects 1 product.


Products: Emc Documentum Thumbnail Server.

## How do I fix CVE-2015-0550?

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

## Is CVE-2015-0550 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0550 and fix it if it is affected.

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

## Sources

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

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