CVE-2016-6644
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 · uneditedEMC Documentum D2 4.5 before patch 15 and 4.6 before patch 03 allows remote attackers to read arbitrary Docbase documents by leveraging knowledge of an r_object_id value.
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 confidenceEMC Documentum D2 contains an Insecure Direct Object Reference (IDOR) vulnerability where the application allows remote unauthenticated attackers to read arbitrary Docbase documents by simply knowing or guessing valid r_object_id values, without proper authorization validation.
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<= 4.5<= 4.6CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Documentum D2 versionCheck the D2 application or installer for the exact version number (typically found in D2 configuration files, installer metadata, or the D2 administrative interface under version information)Affected if Version is 4.5 or lower, or version 4.6 or lower (any version <= 4.5 or <= 4.6 is affected)
-
Confirm D2 is network-accessibleDetermine whether the D2 web interface or API endpoints are accessible from untrusted networks or the public internet without VPN or authentication barriersAffected if D2 is exposed to unauthenticated/network access (the vulnerability requires no authentication to exploit)
-
Verify document access without authenticationAttempt to access a document using a valid r_object_id format (e.g., 0xxxxxxxxxx) through D2 URLs or API endpoints without providing credentialsAffected if Document content is returned without requiring authentication or authorization validation (this confirms the IDOR is present)
-
Check for authorization enforcement on r_object_id accessReview D2 configuration or perform a test: access documents using r_object_id values that should be restricted to privileged users, observing whether the system returns the document content regardless of permissionsAffected if Documents are accessible to unauthenticated users or users without proper document-level permissions simply by knowing the r_object_id
A user is affected if they are running Documentum D2 version 4.5 or lower (or 4.6 or lower) and the D2 interface is accessible without authentication, allowing unauthorized document retrieval via guessed r_object_id values.
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 patches: patch 15 for version 4.5 and patch 03 for version 4.6. These patches add proper authorization checks to validate user permissions before returning document content.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6644 — 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-2016-6644 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