# CVE-2017-15013: Privilege escalation in n/a

> Authenticated users can escalate to superuser privileges by manipulating content objects, requiring immediate patching of Documentum Content Server.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hvv7-ccqx-87f7

## What is CVE-2017-15013?

CVE-2017-15013 is a high-severity vulnerability in n/a, published on 13 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenText Documentum Content Server (formerly EMC Documentum Content Server) through 7.3 contains the following design gap, which allows an authenticated user to gain superuser privileges: Content Server stores information about uploaded files in dmr_content objects, which are queryable and "editable" (before release 7.2P02, any authenticated user was able to edit dmr_content objects; now any authenticated user may delete a dmr_content object and then create a new one with the old identifier) by authenticated users; this allows any authenticated user to replace the content of security-sensitive dmr_content objects (for example, dmr_content related to dm_method objects) and gain superuser privileges.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-15013?

It affects 1 product.


Products: Opentext Documentum Content Server.

## How do I fix CVE-2017-15013?

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

## Is CVE-2017-15013 being exploited?

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

Public exploit code:

- OpenText Documentum Content Server - 'dmr_content' Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-15012](https://insights.sbomify.com/CVE-2017-15012/): Path traversal in n/a (high 8.8)
- [CVE-2017-15276](https://insights.sbomify.com/CVE-2017-15276/): Path traversal in n/a (high 8.8)
- [CVE-2017-7221](https://insights.sbomify.com/CVE-2017-7221/): SQL injection in n/a (high 8.8)
- [CVE-2017-7220](https://insights.sbomify.com/CVE-2017-7220/): Privilege escalation in n/a (high 8.8)
- [CVE-2017-5585](https://insights.sbomify.com/CVE-2017-5585/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15013 and fix it if it is affected.

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

## Sources

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

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