CVE-2015-0518
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 · uneditedThe Properties service in the D2FS web-service component in EMC Documentum D2 3.1 through SP1, 4.0 and 4.1 before 4.1 P22, and 4.2 before P11 allows remote authenticated users to obtain superuser privileges via an unspecified method call that modifies group permissions.
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 confidenceThe D2FS web-service Properties service in EMC Documentum D2 versions 3.1 through SP1, 4.0-4.1 before P22, and 4.2 before P11 contains a privilege escalation vulnerability where an authenticated remote user can obtain superuser privileges through an unspecified method call that modifies group permissions.
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= 3.1= 4.0= 4.1= 4.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm EMC Documentum D2 installationLocate the D2 installation directory on the system, typically found under the Documentum product directories. Check for presence of D2-specific folders and configuration files.Affected if Documentum D2 is not installed on the system
-
Identify installed D2 versionAccess the D2 configuration or about information, typically available through the D2 administrative console, or check version files in the D2 installation directory. Compare the version against the affected ranges: 3.1 through SP1, 4.0-4.1 before P22, or 4.2 before P11.Affected if Installed version falls within 3.1 through SP1, 4.0-4.1 before P22, or 4.2 before P11
-
Verify D2FS web-service is enabledCheck the D2 configuration for the D2FS web-service settings. This service is typically exposed through the application server (WebSphere, WebLogic, or Tomcat) hosting D2. Look for D2FS endpoint configuration in web.xml or similar deployment descriptors.Affected if D2FS web-service is enabled and accessible
-
Assess network accessibility of D2FS endpointDetermine if the D2FS web-service endpoint is exposed to network access. Check firewall rules, application server access restrictions, and whether the service is listening on accessible network interfaces.Affected if D2FS web-service is reachable over the network from untrusted locations
User is affected if D2 is installed with a version in the vulnerable range (3.1 through SP1, 4.0-4.1 before P22, or 4.2 before P11) and the D2FS web-service is network-accessible.
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 4.1 P22 or 4.2 P11 (or later) to remediate this privilege escalation issue. As a compensating control, restrict network access to the D2FS web-service to trusted users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0518 — 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-2015-0518 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