CVE-2014-2518
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 cross-site request forgery (CSRF) vulnerabilities in EMC Documentum WDK before 6.7SP1 P28 and 6.7SP2 before P15 allow remote attackers to hijack the authentication of arbitrary users.
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 confidenceMultiple cross-site request forgery (CSRF) vulnerabilities in EMC Documentum WDK versions prior to 6.7SP1 P28 and 6.7SP2 P15 allow remote unauthenticated attackers to hijack the authentication of legitimate users by tricking them into submitting malicious requests.
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= 6.5= 6.7= 7.0= 7.1= 1.8= 1.9= 6.7= 6.7= 6.7= 1.7= 6.7CVSS 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
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 WDK installation path and versionLocate the WDK installation directory (typically under Documentum/ web/deployment folders) and check the version manifest or about page. In Webtop installations, access the 'About' page or check the version.properties file in the WDK directory.Affected if The installed WDK version is prior to 6.7SP1 P28 or 6.7SP2 P15
-
Check EMC Documentum Webtop versionAccess the Webtop login page and locate the version information, typically found in the footer or in the 'Help > About' section. Alternatively, check the version.txt or build.properties file in the Webtop installation directory.Affected if Version equals 6.7 and is not patched to the fixed patch levels
-
Check EMC Documentum Administrator versionLog into DAdmin (Documentum Administrator) and view the version information from the application or check the installation directory for version metadata.Affected if Version is 6.7, 7.0, or 7.1 without the corresponding security patches applied
-
Check EMC Digital Assets Manager versionAccess the DAm application and locate the version information, typically in the application footer or administrative settings. Check installation logs or version files in the deployment directory.Affected if Version is 6.5 and no patch has been applied
-
Verify CSRF protection statusInspect HTTP responses from Documentum applications for anti-CSRF tokens. Review the application's configuration files (like web.xml) for CSRF token enforcement settings. Test by submitting requests without anti-CSRF tokens.Affected if Application endpoints lack anti-CSRF token validation and the WDK version is unpatched
The environment is affected if any Documentum WDK-based product is installed at version 6.5, 6.7, 7.0, or 7.1 without having applied patch 6.7SP1 P28 or 6.7SP2 P15.
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 6.7SP1 P28 or 6.7SP2 P15 to the affected Documentum WDK installation. Additionally, implement anti-CSRF tokens in application endpoints as a defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2518 — 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-2014-2518 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