Jboss Wildfly Application ServerApplication · Redhat
CVE-2015-3198
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 Undertow module of WildFly 9.x before 9.0.0.CR2 and 10.x before 10.0.0.Alpha1 allows remote attackers to obtain the source code of a JSP page via a "/" at the end of a URL.
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 Undertow web server module in WildFly 9.x before 9.0.0.CR2 and 10.x before 10.0.0.Alpha1 contains an information disclosure vulnerability where requesting a JSP page with a trailing slash (e.g., '/page.jsp/') returns the page's source code instead of executing it. This exposes potentially sensitive application logic, credentials, or configuration details embedded in JSP files.
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
Jboss Wildfly Application ServerApplication
= 9.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 installed WildFly versionCheck the WildFly version by inspecting the $JBOSS_HOME/wildfly/readme.txt file, or by accessing the management console, or running 'grep -r "WildFly" $JBOSS_HOME' in the version manifestsAffected if The version is 9.0.0 exactly, or any 9.x version before 9.0.0.CR2, or any 10.x version before 10.0.0.Alpha1
-
Confirm Undertow is the web serverVerify that Undertow is configured as the web server by checking the standalone.xml configuration file in $JBOSS_HOME/standalone/configuration/ for the undertow subsystemAffected if Undertow is present (this is the default in WildFly 9.x and 10.x)
-
Test for JSP source disclosureDeploy a simple test JSP file (e.g., containing a secret string like '<% String secret = "test123"; %>') and request it with a trailing slash (e.g., 'http://server/test.jsp/'). Use curl or a browser to fetch the URL and check if the JSP source code is returned instead of executed outputAffected if The response contains the raw JSP source code (e.g., '<%' or 'String secret' visible in the response body) rather than executed HTML output
You are affected if your WildFly version is 9.0.0 or any 9.x version before 9.0.0.CR2, or any 10.x version before 10.0.0.Alpha1, AND requesting a JSP with a trailing slash returns the source code instead of executing it.
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 WildFly to version 9.0.0.CR2 or later (for 9.x) or 10.0.0.Alpha1 or later (for 10.x), or apply any subsequent security patches that address this specific vulnerability in the Undertow module.
Fix this in Jboss Wildfly Application Server
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3198 — 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-3198 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