CVE-2018-9117
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 · uneditedWireMock before 2.16.0 contains a vulnerability that allows a remote unauthenticated attacker to access local files beyond the application directory via a specially crafted XML request, aka Directory Traversal.
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 confidenceWireMock before version 2.16.0 contains a directory traversal vulnerability that allows remote unauthenticated attackers to access files outside the application directory through specially crafted XML requests.
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< 2.16.0CVSS 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 if WireMock is installedLocate the WireMock installation directory or running process. Check for wiremock-*.jar files or processes named 'wiremock' running on common ports (8080, 8443).Affected if WireMock is found running in the environment
-
Determine the installed versionRun 'java -jar wiremock.jar --version' from the WireMock directory, or inspect the filename of the wiremock-*.jar file which contains the version number.Affected if The version is below 2.16.0 (for example, 2.15.0, 2.14.0, etc.)
-
Verify XML request handling is enabledConfirm that WireMock is configured to handle XML requests. Check if XML matchers or XML body matching features are in use by reviewing your WireMock mappings or configuration files.Affected if XML request matching is actively used or the endpoint accepts XML content types
-
Check network exposure of the WireMock serviceDetermine if the WireMock HTTP port is exposed to untrusted networks. Review firewall rules, network configuration, or binding settings (--bind-address). Check if the service is accessible without authentication from external IPs.Affected if The WireMock port is reachable from untrusted or external networks without authentication
You are affected if WireMock version is below 2.16.0 AND the XML request handling feature is accessible to remote unauthenticated users.
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 data2.16.0
Upgrade to WireMock version 2.16.0 or later to patch the directory traversal vulnerability.
- Consultation3.0 h
- Implementation3.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 $3,360.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-9117 — 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-9117 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