# CVE-2023-40312: Reflected XSS in multiple JSP files in opennms/opennms

> Attackers can execute arbitrary scripts in victim browsers via reflected XSS in OpenNMS Horizon JSP files, potentially leading to session hijacking or data theft.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Aug 2023
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-chgr-j2p9-jjh8

## What is CVE-2023-40312?

CVE-2023-40312 is a medium-severity cross-site scripting vulnerability in The OpenNMS Group Horizon, published on 14 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Multiple reflected XSS were found on different JSP files with unsanitized parameters in OpenMNS Horizon 31.0.8 and versions earlier than 32.0.2 on multiple platforms that an attacker can modify to craft a malicious XSS payload. The solution is to upgrade to Meridian 2023.1.6, 2022.1.19, 2021.1.30, 2020.1.38 or Horizon 32.0.2 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet. OpenNMS thanks Jordi Miralles Comins for reporting this issue.

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

## Which versions are affected by CVE-2023-40312?

2 open source packages ship an affected version, including org.opennms:opennms-webapp. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.opennms:opennms-webapp` | Maven | From 31.0.8 | 32.0.2 |
| `org.opennms:opennms-webapp` | Maven | From 31.0.8 | 32.0.2 |

Products: Opennms Horizon, Opennms Meridian.

## How do I fix CVE-2023-40312?

Upgrade org.opennms:opennms-webapp to 32.0.2 or later.

## Is CVE-2023-40312 being exploited?

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

## Other vulnerabilities in The OpenNMS Group Horizon

- [CVE-2021-25931](https://insights.sbomify.com/CVE-2021-25931/): Cross-Site Request Forgery in OpenNMS Horizon (high 8.8)
- [CVE-2021-3396](https://insights.sbomify.com/CVE-2021-3396/): OpenNMS Horizon RCE via JEXL2 expression (high 8.8)
- [CVE-2023-0872](https://insights.sbomify.com/CVE-2023-0872/): ROLE_REST can be used to escalate to ROLE_ADMIN via /rest/users (high 8.2)
- [CVE-2023-0870](https://insights.sbomify.com/CVE-2023-0870/): Form Can Be Manipulated with Cross-Site Request Forgery (CSRF) (high 8.1)
- [CVE-2020-11886](https://insights.sbomify.com/CVE-2020-11886/): SQL injection in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-40312 and fix it if it is affected.

What it is: CVE-2023-40312 is a medium-severity cross-site scripting vulnerability in The OpenNMS Group Horizon, published on 14 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-40312 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.opennms:opennms-webapp (Maven): affected from 31.0.8; fixed in 32.0.2
- org.opennms:opennms-webapp (Maven): affected from 31.0.8; fixed in 32.0.2

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-2023-40312/ (Markdown: https://insights.sbomify.com/CVE-2023-40312/index.md)
```

## Sources

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

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