CVE-2014-2504
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 · uneditedEMC Documentum D2 3.1 before P20, 3.1 SP1 before P02, 4.0 before P10, 4.1 before P13, and 4.2 before P01 allows remote authenticated users to bypass intended access restrictions and execute arbitrary Documentum Query Language (DQL) queries by calling (1) a core method or (2) a D2FS web-service method.
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 confidenceEMC Documentum D2 versions prior to specified patch levels contain an access control bypass vulnerability allowing remote authenticated users to execute arbitrary Documentum Query Language (DQL) queries through core methods and D2FS web-service methods, effectively bypassing intended permission restrictions.
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= 3.1= 4.0= 4.1= 4.2CVSS 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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/C:C/I:C/A:C
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 D2 versionLocate the D2 installation directory and check version.info, version.properties, or similar version file. Common paths include $DOCUMENTUM_HOME/d2/ or check the D2 application manifest.Affected if The installed version is 3.1, 4.0, 4.1, or 4.2 (without the specified patches)
-
Verify D2FS web-service endpoint exposureCheck if the D2FS servlet or web-service endpoint is accessible in the application server (e.g., check web.xml for D2FS servlet mapping, or attempt a test request to the D2FS endpoint URL).Affected if The D2FS web-service is exposed and the D2 installation is an unpatched affected version
-
Confirm D2 core methods are available to authenticated usersReview D2 permission configuration files (such as d2fs.properties or d2-config.xml) to verify whether unrestricted DQL execution is permitted through core method calls.Affected if Core methods allow arbitrary DQL query execution without proper permission checks
-
Check application server logs for DQL injection attemptsReview application server logs (e.g., JBoss, WebLogic, WebSphere logs) for unusual or unauthorized DQL query patterns that may indicate exploitation of this vulnerability.Affected if Unusual DQL queries appear in logs from authenticated users performing operations outside their expected scope
-
Verify D2 patch levelIf D2 is installed, check for patch information in the D2 patch directory or by querying the D2 version through its administrative interface or API.Affected if No vendor patches from D2 3.1 P20+, 3.1 SP1 P02+, 4.0 P10+, 4.1 P13+, or 4.2 P01+ are applied
The environment is affected if D2 version 3.1, 4.0, 4.1, or 4.2 is installed without the required patches and D2FS web-service or core methods are accessible to authenticated users.
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.
dbcve · scopedApply the vendor-supplied patches (D2 3.1 P20+, 3.1 SP1 P02+, 4.0 P10+, 4.1 P13+, 4.2 P01+) and verify that DQL query execution respects proper authorization boundaries.
D2 3.1 P20+, D2 3.1 SP1 P02+, D2 4.0 P10+, D2 4.1 P13+, D2 4.2 P01+
- Identify the currently installed Documentum D2 version and patch level
- For D2 3.1: Upgrade to patch P20 or later
- For D2 3.1 SP1: Upgrade to patch P02 or later
- For D2 4.0: Upgrade to patch P10 or later
- For D2 4.1: Upgrade to patch P13 or later
- For D2 4.2: Upgrade to patch P01 or later
- Verify the patch has been applied by checking the D2 version information in the admin console
- Test that the DQL query execution restrictions are properly enforced after patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2504 — 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-2504 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