dbcve.org
Documentum Content ServerApplication · Emc

CVE-2015-4535

HIGH · 7.5 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 →
81/100
Remediation priority · High
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, when __debug_trace__ is configured, allows remote authenticated users to gain super-user privileges by leveraging the ability to read a log file containing a login ticket.

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

In EMC Documentum Content Server, the Java Method Server (JMS) writes login tickets to a log file when the __debug_trace__ debug mode is enabled. Authenticated remote users who can read this log file can extract valid login tickets and use them to escalate privileges to super-user level, achieving unauthorized administrative access.

MitigationDisable the __debug_trace__ configuration setting in production environments and apply the appropriate patch for your version (6.7SP1 P32+, 6.7SP2 P25+, 7.0 P19+, 7.1 P16+, or 7.2 P02+). Additionally, ensure strict file permissions on log directories to prevent unauthorized read access.

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
M
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Complete

AV:N/AC:M/Au:S/C:P/I:P/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 the Content Server version
    Locate the installed Documentum Content Server version using the version detection method for your installation (for example, via dmcl -version command, the installer logs, or the version.ini file in the installation directory)
    Affected if The installed version is 6.7, 7.0, 7.1, or 7.2 without the corresponding patch level (6.7SP1 P32+, 6.7SP2 P25+, 7.0 P19+, 7.1 P16+, or 7.2 P02+)
  2. Verify the __debug_trace__ setting
    Locate the configuration file that controls the __debug_trace__ parameter in your Documentum setup (typically found in the JMS configuration or server configuration files) and check whether it is set to enabled or true
    Affected if The __debug_trace__ debug mode is enabled or set to true in the configuration
  3. Find the JMS log directory
    Identify the Java Method Server log directory path used by your Content Server installation (commonly found under the Documentum installation logs folder or as configured in the JMS configuration)
    Affected if A JMS log directory exists and is accessible on the system
  4. Check log file permissions
    Inspect the file system permissions on the JMS log files and their parent directory to determine which users or groups have read access (use standard file permission inspection commands for your operating system)
    Affected if Log files are readable by users other than the system administrator or the service account running the Content Server

You are affected if your Content Server version is 6.7, 7.0, 7.1, or 7.0 and the __debug_trace__ debug mode is enabled, making login tickets visible in readable log files that can be accessed by unauthorized authenticated users.

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

Disable the __debug_trace__ configuration setting in production environments and apply the appropriate patch for your version (6.7SP1 P32+, 6.7SP2 P25+, 7.0 P19+, 7.1 P16+, or 7.2 P02+). Additionally, ensure strict file permissions on log directories to prevent unauthorized read access.

Fix this in Documentum Content Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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