CVE-2017-14524
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 · uneditedMultiple open redirect vulnerabilities in OpenText Documentum Administrator 7.2.0180.0055 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a (1) URL in the startat parameter to xda/help/en/default.htm or (2) /%09/ (slash encoded horizontal tab slash) followed by a domain in the redirectUrl parameter to xda/component/virtuallinkconnect.
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 confidenceOpenText Documentum Administrator 7.2.0180.0055 contains multiple open redirect vulnerabilities allowing remote attackers to redirect users to arbitrary websites for phishing attacks. The first vector exploits the startat parameter in xda/help/default.htm, while the second uses /%09/ (slash-encoded horizontal tab) followed by a domain in the redirectUrl parameter to xda/component/virtuallinkconnect.
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= 7.2.0180.0055= 6.8.0160.0073CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Documentum Administrator versionAccess the application administrative interface or check the installation directory for version information. Look for version display in the DAB (Documentum Administrator) login page, about dialog, or configuration files in the installation root.Affected if Installed version matches exactly 7.2.0180.0055
-
Identify Documentum Webtop versionAccess the Webtop application or check its installation directory for version information. Look for version details in the login page, help/about section, or configuration files.Affected if Installed version matches exactly 6.8.0160.0073
-
Verify vulnerable endpoint accessibility for Documentum AdministratorAttempt to access the URL pattern xda/help/default.htm with the startat parameter, for example: /xda/help/default.htm?startat=http://example.com. Check if the application accepts and reflects an external domain in the response or redirect.Affected if The application accepts an external URL in the startat parameter and redirects to it, indicating the open redirect is present.
A user is affected if they have Documentum Administrator version 7.2.0180.0055 or Documentum Webtop version 6.8.0160.0073 installed AND the vulnerable endpoints (xda/help/default.htm or xda/component/virtuallinkconnect) are accessible and accept external URLs in the startat or redirectUrl parameters.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation and URL allowlist filtering on the startat and redirectUrl parameters to ensure only trusted, relative URLs are accepted; reject any attempts to inject external domains or encoded path traversal sequences.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14524 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-14524 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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