CVE-2017-15013 json
OpenText Documentum Content Server (formerly EMC Documentum Content Server) through 7.3 contains the following design gap, which allows an…
published 2017-10-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-6488
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.6%
- EPSS 6.6% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
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.
Timeline
- Published
- First public exploit (EDB-43004)
Exploit prediction
6.64% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-43004 OpenText Documentum Content Server - 'dmr_content' Privilege Escalation webapps, 2017-10-17
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
exploit-db.com
/exploits/43004/
exploit
-
securityfocus.com
/bid/101639
vdb-entry
-
seclists.org
/bugtraq/2017/Oct/19
mailing-list, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2017-15013
- NVD CVE-2017-15013
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.