Jboss Enterprise Application PlatformApplication · Redhat
CVE-2015-5188
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 · uneditedCross-site request forgery (CSRF) vulnerability in the Web Console (web-console) in Red Hat Enterprise Application Platform before 6.4.4 and WildFly (formerly JBoss Application Server) before 2.0.0.CR9 allows remote attackers to hijack the authentication of administrators for requests that make arbitrary changes to an instance via vectors involving a file upload using a multipart/form-data submission.
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 confidenceCSRF vulnerability in the Web Console (web-console) of Red Hat Enterprise Application Platform before 6.4.4 and WildFly before 2.0.0.CR9 allows remote attackers to hijack administrator authentication by tricking them into submitting malicious requests via file upload using multipart/form-data submissions, enabling arbitrary changes to the instance.
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 Enterprise Application PlatformApplication
<= 6.4.3
Jboss Wildfly Application ServerApplication
<= 2.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 JBoss EAP or WildFly versionCheck the version banner or read the product version from the installation directory. For EAP, check $JBOSS_HOME/bin/standalone.sh --version or the startup logs. For WildFly, check $WILDFLY_HOME/bin/standalone.sh --version.Affected if The version is JBoss EAP 6.4.3 or earlier, or WildFly 2.0.0.CR8 or earlier (any version up to and including 2.0.0).
-
Verify web console is accessibleConfirm the web console is deployed and reachable by attempting to access the management console URL (typically https://localhost:9993/console or http://localhost:9990/console depending on configuration).Affected if The web console is accessible and the version in step 1 is within the affected range.
-
Check if multipart file upload is enabled in web consoleInspect the web console configuration files in the management realm. Look for multipart/form-data handling in the web console's servlet or filter configuration.Affected if File upload functionality via multipart/form-data is enabled in the web console on an affected version.
A user is affected if they are running JBoss EAP 6.4.3 or earlier, or WildFly 2.0.0 or earlier, with the web console accessible and file upload enabled.
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 Red Hat Enterprise Application Platform 6.4.4 or later, or WildFly 2.0.0.CR9 or later, which contain CSRF protection for the web console file upload functionality.
Fix this in Jboss Enterprise Application Platform
Scoped from the published advisory
- 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-2015-5188 — 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-5188 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