dbcve.org
Documentum AdministratorApplication · Emc

CVE-2008-0656

HIGH · 10.0 CVSS v2.0 Published 2008-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Unrestricted file upload vulnerability in dmclTrace.jsp in EMC Documentum Administrator 5.3.0.313 and Webtop 5.3.0.317 allows remote attackers to overwrite arbitrary files via the filename attribute.

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 · moderate confidence

Unrestricted file upload vulnerability in dmclTrace.jsp in EMC Documentum Administrator and Webtop allows remote attackers to overwrite arbitrary files on the server by manipulating the filename attribute in the upload request. This enables complete compromise of the affected system through arbitrary file write access.

MitigationApply vendor patches from EMC for the affected versions (Documentum Administrator 5.3.0.313 and Webtop 5.3.0.317), or disable/remove the vulnerable dmclTrace.jsp component if patches are unavailable. Restrict network access to the affected interfaces as an interim measure.

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 AdministratorApplication
Affected:= 4.2.8= 5.2.5= 5.2.5_sp2= 5.3.0.313
Documentum WebtopApplication
Affected:= 5.2.5= 5.2.5_sp2= 5.3.0.317

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
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/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. Locate dmclTrace.jsp on the server
    Search the Documentum web application directory for the file dmclTrace.jsp. Typical paths include <Documentum_root>/webapps/ administrator/ or <Documentum_root>/webapps/webtop/ or similar web application directories. Use file system search commands like 'find' or 'dir' to locate this file.
    Affected if The file dmclTrace.jsp exists in the web application directory, indicating the vulnerable component is present.
  2. Verify Documentum Administrator version
    Check the version of EMC Documentum Administrator installed. Look for version files in the installation directory, or access the 'about' or 'version' information through the administrator web interface. Compare the installed version against the affected versions: 4.2.8, 5.2.5, 5.2.5_sp2, or 5.3.0.313.
    Affected if The installed version matches any of: 4.2.8, 5.2.5, 5.2.5_sp2, or 5.3.0.313.
  3. Verify Documentum Webtop version
    Check the version of EMC Documentum Webtop installed. Look for version files in the installation directory, or access the version information through the Webtop web interface. Compare the installed version against the affected versions: 5.2.5, 5.2.5_sp2, or 5.3.0.317.
    Affected if The installed version matches any of: 5.2.5, 5.2.5_sp2, or 5.3.0.317.
  4. Check web interface exposure
    Determine if the Documentum web interfaces (Administrator or Webtop) are accessible from the network. Review firewall rules, web server configuration, and network ACLs to see if ports serving the Documentum applications (typically ports 8080, 8443, or 80/443) are exposed to untrusted networks or the internet.
    Affected if The dmclTrace.jsp file is present AND the web interface is network-accessible from untrusted networks.

The environment is affected if dmclTrace.jsp is present AND either Documentum Administrator version 4.2.8, 5.2.5, 5.2.5_sp2, or 5.3.0.313 is installed, OR Documentum Webtop version 5.2.5, 5.2.5_sp2, or 5.3.0.317 is installed, AND the web interface is network-accessible.

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 vendor patches from EMC for the affected versions (Documentum Administrator 5.3.0.313 and Webtop 5.3.0.317), or disable/remove the vulnerable dmclTrace.jsp component if patches are unavailable. Restrict network access to the affected interfaces as an interim measure.

Fix this in Documentum Administrator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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