# GHSA-2gh6-wc3m-g37f: hermes-management is vulnerable to RCE due to Apache commons-jxpath

> Remote code execution is possible in hermes-management via Apache commons-jxpath when processing user-controlled data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2024

## What is GHSA-2gh6-wc3m-g37f?

GHSA-2gh6-wc3m-g37f is a code injection vulnerability in pl.allegro.tech.hermes:hermes-management, published on 17 Sep 2024. It can be exploited over the network, with no action from the victim.

### Official description

### Impact
hermes-management is vulnerable to RCE when it processes user-controlled data due to using Apache commons-jxpath.

### Patches
Upgrade Hermes to at least hermes-2.2.9

### References
https://hackinglab.cz/en/blog/remote-code-execution-in-jxpath-library-cve-2022-41852/

## Which versions are affected by GHSA-2gh6-wc3m-g37f?

2 open source packages ship an affected version, including pl.allegro.tech.hermes:hermes-management.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pl.allegro.tech.hermes:hermes-management` | Maven | From 0.8.2 | 2.2.9 |
| `pl.allegro.tech.hermes:hermes-management` | Maven | From 0.8.2 | 2.2.9 |

## How do I fix GHSA-2gh6-wc3m-g37f?

Upgrade pl.allegro.tech.hermes:hermes-management to 2.2.9 or later.

## Is GHSA-2gh6-wc3m-g37f being exploited?

There is no known exploitation of GHSA-2gh6-wc3m-g37f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2gh6-wc3m-g37f and fix it if it is affected.

What it is: GHSA-2gh6-wc3m-g37f is a code injection vulnerability in pl.allegro.tech.hermes:hermes-management, published on 17 Sep 2024. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-2gh6-wc3m-g37f in the wild and no public exploit code.

Affected packages and fixed versions:
- pl.allegro.tech.hermes:hermes-management (Maven): affected from 0.8.2; fixed in 2.2.9
- pl.allegro.tech.hermes:hermes-management (Maven): affected from 0.8.2; fixed in 2.2.9

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/GHSA-2gh6-wc3m-g37f/ (Markdown: https://insights.sbomify.com/GHSA-2gh6-wc3m-g37f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2gh6-wc3m-g37f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2gh6-wc3m-g37f/
Summaries are generated and may contain mistakes; the official description above is the record.