VirtualizationApplication · Redhat
CVE-2018-10862
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 · uneditedWildFly Core before version 6.0.0.Alpha3 does not properly validate file paths in .war archives, allowing for the extraction of crafted .war archives to overwrite arbitrary files. This is an instance of the 'Zip Slip' vulnerability.
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 confidenceWildFly Core versions before 6.0.0.Alpha3 fail to validate file paths in .war archive entries during extraction, allowing path traversal attacks. An attacker can craft a malicious .war file with entries containing relative path references (e.g., '../') that cause files to be written outside the intended deployment directory, enabling arbitrary file overwrite on the host system.
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
VirtualizationApplication
= 4.0
Jboss Enterprise Application PlatformApplication
= 7.1.0
Wildfly CoreApplication
<= 5.0.0= 6.0.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 WildFly Core versionRun 'grep -r "JBoss AS" <install_dir>/bin/version.sh' or check the 'wildfly-core.jar' manifest, or inspect the 'org.jboss.as.version' property in <install_dir>/bin/standalone.confAffected if Version is 5.0.0 or lower, or exactly 6.0.0 (note: 6.0.0.Alpha3 and later are NOT affected)
-
Check if using JBoss Enterprise Application PlatformInspect the product.conf file or run the server with the '--version' flag to identify if the installation is EAP 7.1.0Affected if Running JBoss EAP 7.1.0 (which bundles affected WildFly Core)
-
Check Red Hat Virtualization installationQuery the installed packages or check the product version file in the installation directory for Red Hat Virtualization 4.0Affected if Running Red Hat Virtualization 4.0 (which includes affected WildFly components)
-
Verify deployment modeReview the standalone.xml or domain.xml configuration for the 'exploded' deployment attribute or check if .war files are being extracted to the deployment directory (default behavior is vulnerable)Affected if Deployments are being extracted (the default behavior). This is the vulnerable configuration for path traversal exploitation.
A system is affected if WildFly Core version is 5.0.0 or lower, or exactly 6.0.0, or if running JBoss EAP 7.1.0 or Red Hat Virtualization 4.0, AND deployments are being extracted (the default behavior).
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 dataUpgrade to WildFly Core 6.0.0.Alpha3 or later which implements proper path validation for archive entries to prevent path traversal.
Fix this in Virtualization
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10862 — 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-10862 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