Documentum D2Application · Emc

CVE-2016-0888

HIGH · 8.8 CVSS v3.0 Published 2016-04-07
Fix available
A fix is available. Upgrade to after 4.5 or later.
See remediation →
94/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 D2 before 4.6 lacks intended ACLs for configuration objects, which allows remote authenticated users to modify objects 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 · high confidence

EMC Documentum D2 before version 4.6 has a missing access control list (ACL) enforcement vulnerability on configuration objects. Authenticated remote users can modify configuration objects they should not have permission to access, due to intended ACLs not being applied to these objects.

MitigationUpgrade EMC Documentum D2 to version 4.6 or later where proper ACLs are enforced on configuration objects. After upgrade, audit configuration object permissions to confirm the vulnerability is remediated.

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 D2Application
Affected:<= 4.5

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Determine Documentum D2 installed version
    Check the installed version of EMC Documentum D2 in the system. This is typically visible in the D2 installation directory, the Documentum Administrator interface, or the D2 application itself under Help > About or similar version information location.
    Affected if The installed version is 4.5 or any version lower than 4.5
  2. Identify configuration objects in D2
    Locate configuration objects within the EMC Documentum D2 application. These are typically objects that store application settings, workflows, or system configurations managed through the D2 configuration management interface.
    Affected if Configuration objects exist in the D2 environment and the version is 4.5 or lower
  3. Verify ACL enforcement on configuration objects
    Attempt to verify whether access control lists are being properly applied to configuration objects. This may involve reviewing the ACL properties on configuration objects through the Documentum administrator tools or D2 configuration interface to confirm if ACLs are enforced as intended.
    Affected if ACLs are not being applied or enforced on configuration objects, meaning any authenticated user can potentially modify them regardless of intended permissions
  4. Test unauthorized access to configuration objects
    As an authenticated user with limited permissions, attempt to access or modify configuration objects that should be restricted based on the user's role. Document the results to determine if permission boundaries are being enforced.
    Affected if Users can modify configuration objects they should not have permission to access, confirming the missing ACL enforcement vulnerability is present

A user is affected if EMC Documentum D2 version 4.5 or lower is installed AND authenticated users can access or modify configuration objects that should be restricted by ACLs.

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
Upgrade available Upgrade to a release after 4.5
Interim mitigation

Upgrade EMC Documentum D2 to version 4.6 or later where proper ACLs are enforced on configuration objects. After upgrade, audit configuration object permissions to confirm the vulnerability is remediated.

Fix this in Documentum D2 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0888 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-0888 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