CVE-2013-0937
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 · uneditedSession fixation vulnerability in EMC Documentum Webtop before 6.7 SP2, Documentum WDK before 6.7 SP2, Documentum Taskspace before 6.7 SP2, and Documentum Records Manager before 6.7 SP2 allows remote attackers to hijack web sessions via unspecified vectors.
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 confidenceSession fixation vulnerability in EMC Documentum products allows remote attackers to hijack web sessions by setting or fixing a user's session ID before authentication. After the user logs in, the attacker can use the predetermined session ID to gain unauthorized access to the authenticated session.
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= 6.7= 6.7= 6.7= 6.7CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed EMC Documentum componentsCheck the installed applications on your system for Documentum Webtop, WDK, Taskspace, or Records Manager. Look in the application installation directory or check system inventory for these component names.Affected if Any of these four components (Webtop, WDK, Taskspace, Records Manager) are installed on the system
-
Determine the installed version of Documentum componentsLocate the version information for each installed Documentum component. Check the component's about page, version file, or installation manifest. Common locations include the component's installation directory or the dm_server_config.xml file.Affected if The installed version is exactly 6.7 for any of the affected components (Webtop, WDK, Taskspace, or Records Manager)
-
Determine if the Documentum web interface is network-accessible. Check whether ports for Webtop (typically 8080 or 8443) or the WDK servlet are exposed to netwoAffected if The web interface is accessible from untrusted networks, making session fixation exploitation possible
-
Inspect session ID handling configurationExamine the web application configuration files (such as web.xml) for the affected component to see how session IDs are managed. Look for session tracking configuration and whether session fixation protection is implemented.Affected if Session IDs are not regenerated upon authentication - the same session ID used before login remains valid after successful authentication
Your environment is affected if you have any of the four Documentum components (Webtop, WDK, Taskspace, Records Manager) installed at exactly version 6.7 with an accessible web interface that does not regenerate session IDs after authentication.
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.
From vendor dataApply vendor patch 6.7 SP2 to all affected EMC Documentum components (Webtop, WDK, Taskspace, and Records Manager). Consider implementing session ID regeneration upon authentication as an additional defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0937 — 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-2013-0937 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