dbcve.org
Documentum Foundation ServicesApplication · Emc

CVE-2014-0622

HIGH · 9.0 CVSS v2.0 Published 2014-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
The web service in EMC Documentum Foundation Services (DFS) 6.5 through 6.7 before 6.7 SP1 P22, 6.7 SP2 before P08, 7.0 before P12, and 7.1 before P01 does not properly implement content uploading, which allows remote authenticated users to bypass intended content access restrictions 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 confidence

The web service in EMC Documentum Foundation Services (DFS) versions 6.5 through 6.7 before 6.7 SP1 P22, 6.7 SP2 before P08, 7.0 before P12, and 7.1 before P01 has a flaw in content uploading implementation that allows authenticated remote users to bypass intended content access restrictions.

MitigationApply the appropriate patch (6.7 SP1 P22, 6.7 SP2 P08, 7.0 P12, or 7.1 P01) and conduct access control verification testing to confirm content restrictions are enforced.

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 Foundation ServicesApplication
Affected:= 6.5= 6.6= 6.7= 7.0= 7.1

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

AV:N/AC:L/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. Verify EMC Documentum Foundation Services is installed
    Look for DFS installation directories (typically under /opt/documentum or C:\Documentum) or check for running DFS services using system commands like 'sc query' on Windows or 'ps aux' on Unix/Linux.
    Affected if DFS is not installed on the system.
  2. Identify the installed DFS version
    Check the version file in the DFS installation directory, such as a version.properties file, or use the DFS command-line tool if available (for example, 'dm version' or similar). Compare the version against the affected ranges: 6.5, 6.6, 6.7, 7.0, or 7.1.
    Affected if The installed version is 6.5, 6.6, 6.7, 7.0, or 7.1 without the patched versions (6.7 SP1 P22, 6.7 SP2 P08, 7.0 P12, or 7.1 P01).
  3. Confirm the DFS web service is accessible
    Check if the DFS web service endpoint is exposed by reviewing the application server configuration (such as web.xml or server.xml) and attempting to access the DFS web service URL (commonly under /services/ on the application server).
    Affected if The DFS web service endpoint is accessible and responds to requests.
  4. Verify content upload functionality is enabled
    Review the DFS configuration files (such as services-config.xml or similar) to determine if the content upload/upload service module is enabled and accessible to authenticated users.
    Affected if The content upload service is enabled and accessible to authenticated users.
  5. Review content access control configuration
    Examine the DFS and underlying Documentum repository access control settings to verify if proper content access restrictions are in place for uploaded content. Check ACL configurations in the repository.
    Affected if Content access controls appear to be misconfigured or can be bypassed by authenticated users during upload operations.

A system is affected if EMC Documentum Foundation Services versions 6.5, 6.6, 6.7, 7.0, or 7.1 are installed with the web service and content upload functionality enabled, and the installed version is below the patched versions (6.7 SP1 P22, 6.7 SP2 P08, 7.0 P12, or 7.1 P01).

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate patch (6.7 SP1 P22, 6.7 SP2 P08, 7.0 P12, or 7.1 P01) and conduct access control verification testing to confirm content restrictions are enforced.

Recommended fix High confidence

Upgrade to minimum fixed patch levels: 6.7 SP1 P22, 6.7 SP2 P08, 7.0 P12, or 7.1 P01 (or later supported releases)

  1. Identify the current Documentum Foundation Services version and service pack level in use
  2. For DFS 6.5: Upgrade to version 6.7 SP1 P22 or later (recommended: upgrade to a supported version like 6.7 SP2 P08 or later)
  3. For DFS 6.6: Upgrade to version 6.7 SP1 P22 or later (recommended: upgrade to a supported version like 6.7 SP2 P08 or later)
  4. For DFS 6.7: If on SP1, upgrade to P22 or later; if on SP2, upgrade to P08 or later
  5. For DFS 7.0: Upgrade to P12 or later
  6. For DFS 7.1: Upgrade to P01 or later
  7. After upgrading, verify that content access restrictions are properly enforced for authenticated users
  8. Test the content uploading functionality to confirm proper permission controls are in place

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Documentum Foundation Services Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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