dbcve.org
Documentum TaskspaceApplication · Emc

CVE-2014-0629

HIGH · 8.5 CVSS v2.0 Published 2014-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
EMC Documentum TaskSpace (TSP) 6.7SP1 before P25 and 6.7SP2 before P11 does not properly handle the interaction between the dm_world group and the dm_superusers_dynamic group, which allows remote authenticated users to obtain sensitive information and gain privileges in opportunistic circumstances by leveraging an incorrect group-addition implementation.

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

EMC Documentum TaskSpace (TSP) 6.7SP1 before P25 and 6.7SP2 before P11 contains a group membership logic flaw where the interaction between dm_world and dm_superusers_dynamic groups is improperly handled. This allows remote authenticated users to gain elevated privileges and access sensitive information due to an incorrect group-addition implementation.

MitigationApply vendor patches: update to TSP 6.7SP1 P25 or later, or TSP 6.7SP2 P11 or later. After patching, verify that group membership assignments function correctly and that privilege boundaries are enforced as intended.

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 TaskspaceApplication
Affected:= 6.7

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

AV:N/AC:M/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 installed TaskSpace version
    Query the Documentum repository or check TSP application metadata for the exact version number (e.g., 6.7, 6.7SP1, 6.7SP2) and patch level (P-number)
    Affected if Version is 6.7SP1 before P25, or 6.7SP2 before P11, or unpatched 6.7 base release
  2. Verify dm_world group configuration
    Query the Documentum content server for the dm_world group definition and its member list using DQL or the DMCLT interface
    Affected if The dm_world group exists and contains unexpected members or is improperly linked to privileged group logic
  3. Check dm_superusers_dynamic group settings
    Query the repository for the dm_superusers_dynamic group configuration and examine its relationship to other system groups
    Affected if The dm_superusers_dynamic group is present and has membership rules that interact with dm_world in a way that grants elevated access
  4. Inspect group membership assignments
    Review the group membership records to determine if users added to dm_world are incorrectly being granted superuser privileges through the dm_superusers_dynamic relationship
    Affected if Users in dm_world are receiving elevated privileges or access to sensitive information beyond what dm_world membership should normally provide
  5. Verify privilege boundary enforcement
    Test or audit whether standard users in dm_world can access objects or functions restricted to dm_superusers_dynamic group members
    Affected if Users with only dm_world membership can perform actions or access data that should require dm_superusers_dynamic membership

A system is affected if it runs an unpatched version of Documentum TaskSpace 6.7SP1 before P25 or 6.7SP2 before P11 AND the dm_world group is improperly granting elevated privileges through interaction with dm_superusers_dynamic.

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: update to TSP 6.7SP1 P25 or later, or TSP 6.7SP2 P11 or later. After patching, verify that group membership assignments function correctly and that privilege boundaries are enforced as intended.

Fix this in Documentum Taskspace Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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