CVE-2017-14525
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 Webtop 6.8.0160.0073 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 Webtop 6.8.0160.0073 contains multiple open redirect vulnerabilities. Attackers can manipulate the startat parameter in xda/help/en/default.htm or the redirectUrl parameter in xda/component/virtuallinkconnect (using /%09/ encoding) to redirect users to arbitrary external websites, facilitating phishing attacks.
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 installed Documentum Webtop versionCheck the Webtop installation directory for version files or examine the application banner/About page. Common locations include the WAR file or the installation root containing files like version.txt or build.properties.Affected if The installed version equals exactly 6.8.0160.0073
-
Identify installed Documentum Administrator versionCheck the Documentum Administrator installation for version information, typically found in version metadata files or the application About page.Affected if The installed version equals exactly 7.2.0180.0055
-
Verify vulnerable endpoint accessibilityAttempt to access the paths /xda/help/en/default.htm and /xda/component/virtuallinkconnect on the Webtop server to confirm the application is deployed and these endpoints exist.Affected if The application responds on these paths and accepts redirect parameters
-
Check redirect parameter processingInspect HTTP traffic or application logs to determine if the startat parameter in the help endpoint and the redirectUrl parameter in virtuallinkconnect are processed without validation.Affected if The application accepts and processes these redirect parameters without validating they point to internal domains only
You are affected if you are running exactly version 6.8.0160.0073 of Documentum Webtop or exactly version 7.2.0180.0055 of Documentum Administrator and the vulnerable endpoints are accessible and process redirect 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 URL allowlist validation for redirect parameters, rejecting any URLs that do not point to trusted internal domains or explicitly approved external sites.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14525 — 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-14525 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