CVE-2015-4529
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 · uneditedOpen redirect vulnerability in EMC Documentum WebTop before 6.8P02, Documentum Administrator before 7.2P01, Documentum Digital Assets Manager through 6.5SP6, Documentum Web Publishers through 6.5SP7, and Documentum Task Space through 6.7SP2 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a crafted URL.
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 · moderate confidenceOpen redirect vulnerability in multiple EMC Documentum products (WebTop before 6.8P02, Documentum Administrator before 7.2P01, Digital Assets Manager through 6.5SP6, Web Publishers through 6.5SP7, and Task Space through 6.7SP2) allows remote attackers to redirect users to arbitrary websites via crafted URLs for 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<= 6.5<= 6.7<= 6.5<= 6.8CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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 productsReview your environment for any of the following Documentum applications: Documentum Administrator, Digital Asset Manager, Task Space, Web Publisher, or WebTop. Check installation directories, application inventories, or deployment records to list which products are present.Affected if Any of the five affected products (WebTop, Documentum Administrator, Digital Assets Manager, Web Publishers, or Task Space) are installed in the environment.
-
Determine installed product versionsLocate the version information for each identified Documentum product. Common methods include checking the product's About dialog, version file in the installation directory, or the application's login screen footer. Compare these version numbers against the affected ranges: WebTop <= 6.8, Documentum Administrator <= 7.2, Digital Asset Manager <= 6.5, Task Space <= 6.7, Web Publisher <= 6.5.Affected if Any installed product version falls at or below its specified threshold (WebTop <= 6.8, DAdmin <= 7.2, DAM <= 6.5, Task Space <= 6.7, Web Publisher <= 6.5).
-
Verify web interface exposureConfirm whether the Documentum web interfaces are accessible over HTTP/HTTPS. Test access to known web entry points such as /webtop, /da, /dam, /taskspace, or /webpublisher for the respective products.Affected if The web interface is exposed and reachable, making the open redirect vulnerability accessible to remote attackers.
-
Inspect URL redirect parameters in useReview web access logs or proxy logs for requests containing redirect-related parameters such as 'redirect=', 'returnurl=', 'next=', or 'url=' pointing to the Documentum web applications. Identify if applications are processing user-controlled redirect targets.Affected if The application processes redirect parameters that accept external URLs, enabling the open redirect attack vector.
You are affected if any Documentum product from the list is installed at a version at or below its threshold and has an exposed web interface that handles 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 dataApply vendor patches for all affected Documentum products to the specified version thresholds or implement strict URL redirect validation to ensure redirect targets remain within trusted domains.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4529 — 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-2015-4529 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