# CVE-2018-8031: Apache TomEE console vulnerable to Cross-site Scripting

> An XSS vulnerability in the Apache TomEE console allows attackers to execute JavaScript via malicious URLs, affecting users who have the webapp enabled.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fg44-w3fr-hgxv

## What is CVE-2018-8031?

CVE-2018-8031 is a medium-severity cross-site scripting vulnerability in Apache TomEE, published on 23 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-8031?

2 open source packages ship an affected version, including org.apache.tomee:tomee-webapp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomee:tomee-webapp` | Maven | All versions | 7.0.5 |
| `org.apache.tomee:tomee-webapp` | Maven | All versions | 7.0.5 |

Products: Apache Tomee.

## How do I fix CVE-2018-8031?

Upgrade org.apache.tomee:tomee-webapp to 7.0.5 or later.

## Is CVE-2018-8031 being exploited?

There is no known exploitation of CVE-2018-8031 in the wild and no public exploit code.

## Other vulnerabilities in Apache TomEE

- [CVE-2020-13931](https://insights.sbomify.com/CVE-2020-13931/): Remote code execution in Apache TomEE (critical 9.8)
- [CVE-2020-11969](https://insights.sbomify.com/CVE-2020-11969/): Missing Authentication for Critical Function in Apache TomEE (critical 9.8)
- [CVE-2019-13990](https://insights.sbomify.com/CVE-2019-13990/): XML external entity injection in Terracotta Quartz Scheduler (critical 9.8)
- [CVE-2016-0779](https://insights.sbomify.com/CVE-2016-0779/): Deserialization in n/a (critical 9.8)
- [CVE-2019-17359](https://insights.sbomify.com/CVE-2019-17359/): Out-of-Memory Error in Bouncy Castle Crypto (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8031 and fix it if it is affected.

What it is: CVE-2018-8031 is a medium-severity cross-site scripting vulnerability in Apache TomEE, published on 23 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-8031 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomee:tomee-webapp (Maven): affected all versions; fixed in 7.0.5
- org.apache.tomee:tomee-webapp (Maven): affected all versions; fixed in 7.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-8031/ (Markdown: https://insights.sbomify.com/CVE-2018-8031/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8031
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8031
- OSV: https://osv.dev/vulnerability/CVE-2018-8031

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-8031/
Summaries are generated and may contain mistakes; the official description above is the record.