dbcve.org
Documentum AdministratorApplication · Opentext

CVE-2017-14526

HIGH · 8.8 CVSS v3.0 Published 2017-09-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple XML external entity (XXE) vulnerabilities in the OpenText Documentum Administrator 7.2.0180.0055 allow remote authenticated users to list the contents of arbitrary directories, read arbitrary files, cause a denial of service, or, on Windows, obtain Documentum user hashes via a (1) crafted DTD, involving unspecified XML structures in a request to xda/com/documentum/ucf/server/transport/impl/GAIRConnector or crafted XML file in a MediaProfile file (2) import or (3) check in.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple XXE vulnerabilities in OpenText Documentum Administrator 7.2.0180.0055 allow authenticated remote attackers to exploit unsanitized XML input via three vectors: crafted DTD in UC transport requests, and malicious XML in MediaProfile file imports and check-ins. Attackers can read arbitrary files, list directories, cause DoS, and on Windows extract Documentum user password hashes.

MitigationApply the vendor patch for CVE-2017-14526 to upgrade Documentum Administrator, and/or configure XML parsers to disable external entity processing and enable XXE injection protection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Documentum AdministratorApplication
Affected:= 7.2.0180.0055
Documentum WebtopApplication
Affected:= 6.8.0160.0073

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Documentum Administrator version
    Check the application version through the DmServlet or about page in the Documentum Administrator web interface, or examine the installed package/version file in the Documentum installation directory.
    Affected if Version matches exactly 7.2.0180.0055 (Documentum Administrator)
  2. Identify installed Documentum Webtop version
    Check the webtop application version through the WAR file properties, or examine the version manifest in the deployed Webtop web application directory.
    Affected if Version matches exactly 6.8.0160.0073 (Documentum Webtop)
  3. Verify UC transport endpoint is exposed
    Inspect whether the UC (Universal Chorus) transport service endpoint is accessible and enabled in the Documentum Administrator configuration. Check the servlet or service mapping for UC transport handlers in the web.xml or similar deployment descriptor.
    Affected if UC transport requests can be submitted to the server without additional authentication beyond basic Documentum login
  4. Verify MediaProfile import functionality is accessible
    Check if the MediaProfile import feature is enabled and accessible to authenticated users through the Documentum Administrator or Webtop interface. This typically involves the XML-based import functionality for profile configurations.
    Affected if Authenticated users can import MediaProfile XML files without XXE protection being applied
  5. Verify check-in functionality accepts XML payloads
    Determine if the document check-in process accepts and processes XML content without sanitization. This may involve examining the check-in servlet or API endpoint configuration.
    Affected if Check-in operations process unsanitized XML input from authenticated users

User is affected if running Documentum Administrator exactly at version 7.2.0180.0055 or Webtop exactly at version 6.8.0160.0073 AND the UC transport, MediaProfile import, or check-in features are accessible to authenticated users without XML entity processing disabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CVE-2017-14526 to upgrade Documentum Administrator, and/or configure XML parsers to disable external entity processing and enable XXE injection protection.

Fix this in Documentum Administrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-14526 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data