CVE-2018-6885
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 · uneditedAn issue was discovered in MicroStrategy Web Services (the Microsoft Office plugin) before 10.4 Hotfix 7, and before 10.11. The vulnerability is unauthenticated and leads to access to the asset files with the MicroStrategy user privileges. (This includes the credentials to access the admin dashboard which may lead to RCE.) The path traversal is located in a SOAP request in the web service component.
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 confidenceUnauthenticated path traversal vulnerability in MicroStrategy Web Services SOAP component allows attackers to access sensitive asset files including credentials by manipulating path sequences in SOAP requests, potentially enabling RCE through admin dashboard access.
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< 10.4>= 10.5, < 10.11= 10.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify MicroStrategy Web Services installationCheck for MicroStrategy Web application files or running services. Common paths include C:\Program Files\MicroStrategy\Web or /opt/microstrategy/Web. Look for the 'Web Services' or 'SOAP' component in the installation directory.Affected if MicroStrategy Web Services is installed and the SOAP component is present
-
Determine installed MicroStrategy versionCheck the version of MicroStrategy Web. The version is typically stored in a version file or can be retrieved from the MicroStrategy Administrator. Common locations include a version.txt file in the Web folder or check the 'About' page in MicroStrategy Enterprise Manager.Affected if The installed version is < 10.4, = 10.4, or >= 10.5 but < 10.11
-
Verify SOAP endpoint is exposedCheck if the MicroStrategy Web Services SOAP endpoint is accessible without authentication. The typical endpoint URL pattern is /MicroStrategyWS/axis2/services or similar SOAP service paths. Attempt a GET request to common SOAP paths to confirm accessibility.Affected if The SOAP endpoint is reachable over the network without authentication (this is the default unauthenticated access vector for the vulnerability)
-
Check network exposure of Web ServicesReview firewall rules and network configuration to determine if the MicroStrategy Web Services are accessible from untrusted networks. Verify which IP addresses or subnets can reach the SOAP endpoint.Affected if The SOAP endpoint is accessible from untrusted networks or the internet
A user is affected if they have MicroStrategy Web Services installed with a version before 10.11 (including version 10.4 and versions below 10.4) and the SOAP endpoint is accessible without authentication.
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.
dbcve · scoped10.410.11
Upgrade to MicroStrategy 10.4 Hotfix 7 or later, or 10.11 or later. If immediate patching is not possible, restrict access to the web services component via network segmentation or firewall rules.
10.4 Hotfix 7 or 10.11 and later
- Identify your current MicroStrategy Web Services version by checking the administration console or the installed software
- For versions < 10.4: Upgrade to version 10.4 and apply Hotfix 7, or upgrade directly to version 10.11 or later
- For versions 10.5 through 10.10: Upgrade to version 10.11 or later (recommended) or upgrade to version 10.4 and apply Hotfix 7
- For version 10.4 without hotfix: Apply Hotfix 7 to version 10.4, or upgrade to version 10.11 or later
- After upgrading, verify the patch was applied successfully by checking the MicroStrategy version information in the administration console
- Test that the SOAP endpoint no longer accepts path traversal requests (e.g., attempts to access ../../etc/passwd should fail)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6885 — 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-2018-6885 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