dbcve.org
CenterstageApplication · Emc

CVE-2014-2510

MEDIUM · 6.8 CVSS v2.0 Published 2014-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The JAXB XML parser in EMC Documentum Foundation Services (DFS) 6.6 before P39, 6.7 SP1 before P28, and 6.7 SP2 before P15, as used in My Documentum for Desktop, My Documentum for Microsoft Outlook, and CenterStage, allows remote authenticated users to read arbitrary files via an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

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 confidence

The JAXB XML parser in EMC Documentum Foundation Services contains an XML External Entity (XXE) vulnerability. Remote authenticated users can exploit this by crafting malicious XML that includes external entity declarations to read arbitrary files from the server's filesystem.

MitigationApply the appropriate patches to Documentum Foundation Services: P39 for version 6.6, P28 for 6.7 SP1, or P15 for 6.7 SP2. Alternatively, disable external entity processing in the JAXB configuration.

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
CenterstageApplication
Affected:= 1.2
Documentum Foundation ServicesApplication
Affected:= 6.6= 6.7
My Documentum For DesktopApplication
Affected:= 6.7.2
My Documentum For Microsoft OutlookApplication
Affected:= 6.7= 6.7.1= 6.7.3

CVSS 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
None
Availability
None

AV:N/AC:L/Au:S/C:C/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product
    Locate EMC Documentum Foundation Services, Centerstage, My Documentum For Desktop, or My Documentum For Microsoft Outlook installations on the system. Check program directories or installed applications list.
    Affected if Any of the affected products (Centerstage 1.2, DFS 6.6/6.7, My Documentum For Desktop 6.7.2, or My Documentum For Microsoft Outlook 6.7/6.7.1/6.7.3) are installed.
  2. Verify product version
    Check the installed version of the EMC product against the affected version list. Look in the product's About or version information panel, or check version metadata files in the installation directory.
    Affected if The installed version matches exactly: Centerstage 1.2, DFS 6.6 or 6.7, My Documentum For Desktop 6.7.2, or My Documentum For Microsoft Outlook 6.7, 6.7.1, or 6.7.3.
  3. Confirm JAXB XML parser is in use
    Examine application logs or configuration to determine if the JAXB XML parser is being used for processing XML requests. Check for JAXB libraries (jaxb-api.jar, jaxb-impl.jar) in the installation or application classpath.
    Affected if JAXB is actively used for XML parsing within the affected application.
  4. Check JAXB configuration for external entity processing
    Locate and inspect the JAXB configuration files (typically XML parser configuration or properties files). Look for settings related to external entity processing, such as XMLConstants.ACCESS_EXTERNAL_DTD, XMLConstants.ACCESS_EXTERNAL_SCHEMA, or similar parser configuration properties.
    Affected if External entity processing is enabled or not explicitly disabled in the JAXB/XML parser configuration.

You are affected if you have any of the listed product versions installed with JAXB XML parsing enabled and external entity processing is allowed in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate patches to Documentum Foundation Services: P39 for version 6.6, P28 for 6.7 SP1, or P15 for 6.7 SP2. Alternatively, disable external entity processing in the JAXB configuration.

Fix this in Centerstage Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2510 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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