dbcve.org
Documentum Content ServerApplication · Emc

CVE-2015-4534

HIGH · 9.0 CVSS v2.0 Published 2015-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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
Java Method Server (JMS) in EMC Documentum Content Server before 6.7SP1 P32, 6.7SP2 before P25, 7.0 before P19, 7.1 before P16, and 7.2 before P02 allows remote authenticated users to execute arbitrary code by forging a signature for a query string that lacks the method_verb parameter.

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

Vulnerability in EMC Documentum Content Server's Java Method Server (JMS) allows remote authenticated users to execute arbitrary code by forging signatures for query strings lacking the method_verb parameter, effectively bypassing authentication controls.

MitigationApply the specific patches for each affected version: 6.7SP1 P32 or later, 6.7SP2 P25 or later, 7.0 P19 or later, 7.1 P16 or later, or 7.2 P02 or later.

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
Documentum Content ServerApplication
Affected:= 6.7= 7.0= 7.1= 7.2

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
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 checks

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

  1. Identify Documentum Content Server installation
    Locate the Documentum installation directory and confirm the presence of Content Server components (look for dm_document objects, repository configurations, or dm_server processes)
    Affected if EMC Documentum Content Server is installed on the system
  2. Determine the installed Content Server version
    Query the Content Server version using the dm_version script, dmadmin command, or check version files in the installation directory (such as version.txt or dmcl.ini)
    Affected if The installed version is 6.7, 7.0, 7.1, or 7.2 base release without the corresponding security patches
  3. Check for applied security patches
    Review installed patches using the Documentum patch installer (dm_install_patches) or check for patch directories in the installation path
    Affected if The system lacks patches: 6.7SP1 P32+, 6.7SP2 P25+, 7.0 P19+, 7.1 P16+, or 7.2 P02+
  4. Verify Java Method Server (JMS) is enabled
    Confirm JMS is configured and running (check for jms process, JMS configuration files in the installation, or via Documentum Administrator console)
    Affected if JMS component is enabled and running

The environment is affected if EMC Documentum Content Server versions 6.7, 7.0, 7.1, or 7.2 are running without the required security patches and the Java Method Server component is enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the specific patches for each affected version: 6.7SP1 P32 or later, 6.7SP2 P25 or later, 7.0 P19 or later, 7.1 P16 or later, or 7.2 P02 or later.

Recommended fix High confidence

7.2 P02 (or latest available 7.x patch containing security fix)

  1. Upgrade Content Server to one of the following patched versions: 6.7SP1 P32, 6.7SP2 P25, 7.0 P19, 7.1 P16, or 7.2 P02
  2. If running older versions, upgrade to the nearest patched version listed above
  3. After upgrading, verify the Java Method Server (JMS) configuration and restart JMS services
  4. Confirm the upgrade by reviewing the JMS signature validation behavior for query strings lacking the method_verb parameter
Caveat Patching may require downtime; test in non-production environment first to verify compatibility with existing customizations and integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Documentum Content Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4534 — 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-2015-4534 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