TomeeApplication · Apache
CVE-2018-8031
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 Apache TomEE console (tomee-webapp) has a XSS vulnerability which could allow javascript to be executed if the user is given a malicious URL. This web application is typically used to add TomEE features to a Tomcat installation. The TomEE bundles do not ship with this application included. This issue can be mitigated by removing the application after TomEE is setup (if using the application to install TomEE), using one of the provided pre-configured bundles, or by upgrading to TomEE 7.0.5. This issue is resolve in this commit: b8bbf50c23ce97dd64f3a5d77f78f84e47579863.
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 Apache TomEE console (tomee-webapp) contains a cross-site scripting (XSS) vulnerability that allows arbitrary JavaScript execution in user browsers when they visit a maliciously crafted URL. This affects the web application used to add TomEE features to Tomcat installations.
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
TomeeApplication
< 7.0.5CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the installed Apache TomEE versionLocate the version file or check the release. Common locations: $TOMEE_HOME/RELEASE.NOTES, $TOMEE_HOME/VERSION, or the tomee-webapp version manifest in webapps/tomee-webapp/META-INF/MANIFEST.MF. Alternatively, check the main TomEE jar file names in the lib directory.Affected if The installed version is any release prior to 7.0.5 (for example, 7.0.4, 7.0.3, 7.0.2, 7.0.1, 7.0.0, or 1.7.x versions).
-
Verify if the tomee-webapp application is deployedInspect the webapps directory (commonly $TOMEE_HOME/webapps/) for the tomee-webapp folder or the tomee-webapp.war archive. Also check if the context is listed in the conf/server.xml file.Affected if The tomee-webapp directory or WAR file exists in the webapps folder, indicating the console is installed.
-
Confirm the web console is accessibleAttempt to access the TomEE console URL (typically http://hostname:port/tomee-webapp/ or http://hostname:port/) and verify it returns a login page or console interface. Check the conf/server.xml for enabled application contexts.Affected if The console responds with a login page or console interface, meaning the vulnerable component is active and reachable over the network.
A user is affected if they are running any Apache TomEE version prior to 7.0.5 AND the tomee-webapp application is deployed and accessible.
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 data7.0.5
Remove the tomee-webapp application after initial TomEE configuration, use pre-configured TomEE bundles instead, or upgrade to TomEE 7.0.5 or later where the vulnerability is patched.
Fix this in Tomee
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8031 — 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-8031 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