# CVE-2022-45470: Apache Hama allows XSS and information disclosure

> Attackers can exploit missing input validation in Apache Hama to perform XSS and path traversal, leading to information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-4wfh-48v4-3r84

## What is CVE-2022-45470?

CVE-2022-45470 is a high-severity cross-site scripting vulnerability in Apache Hama, published on 21 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

missing input validation in Apache Hama may cause information disclosure through path traversal and XSS. Since Apache Hama is EOL, we do not expect these issues to be fixed.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-45470?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.hama:hama-core` | Maven | All versions to 0.7.1 | None |
| `org.apache.hama:hama-core` | Maven | All versions to 0.7.1 | None |

Products: Apache Hama.

## How do I fix CVE-2022-45470?

No fix has been published for CVE-2022-45470 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-45470 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45470 and fix it if it is affected.

What it is: CVE-2022-45470 is a high-severity cross-site scripting vulnerability in Apache Hama, published on 21 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45470 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.hama:hama-core (Maven): affected all versions up to 0.7.1; no fix listed
- org.apache.hama:hama-core (Maven): affected all versions up to 0.7.1; no fix listed

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

## Sources

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

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