# CVE-2017-2594: Path Traversal in io.hawt:project

> An attacker can exploit a path traversal flaw in hawtio to trigger a NullPointerException and disclose sensitive stack trace information.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9g8w-pjpr-prr4

## What is CVE-2017-2594?

CVE-2017-2594 is a medium-severity path traversal vulnerability in unspecified hawtio, published on 8 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

hawtio before versions 2.0-beta-1, 2.0-beta-2 2.0-m1, 2.0-m2, 2.0-m3, and 1.5 is vulnerable to a path traversal that leads to a NullPointerException with a full stacktrace. An attacker could use this flaw to gather undisclosed information from within hawtio's root.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2017-2594?

2 open source packages ship an affected version, including io.hawt:project. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.hawt:project` | Maven | All versions | 1.5.0 |
| `io.hawt:project` | Maven | All versions | 1.5.0 |

Products: Hawt Hawtio.

## How do I fix CVE-2017-2594?

Upgrade io.hawt:project to 1.5.0 or later.

## Is CVE-2017-2594 being exploited?

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

## Other vulnerabilities in unspecified hawtio

- [CVE-2019-9827](https://insights.sbomify.com/CVE-2019-9827/): Server-Side Request Forgery in Hawt Hawtio (critical 9.8)
- [CVE-2014-0121](https://insights.sbomify.com/CVE-2014-0121/): Missing authorization in n/a (critical 9.8)
- [CVE-2014-0120](https://insights.sbomify.com/CVE-2014-0120/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-7556](https://insights.sbomify.com/CVE-2017-7556/): Cross-Site Request Forgery in hawtio (high 8.8)
- [CVE-2017-2589](https://insights.sbomify.com/CVE-2017-2589/): Insecure cookie sharing in Hawtio (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2594 and fix it if it is affected.

What it is: CVE-2017-2594 is a medium-severity path traversal vulnerability in unspecified hawtio, published on 8 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2594 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.hawt:project (Maven): affected all versions; fixed in 1.5.0
- io.hawt:project (Maven): affected all versions; fixed in 1.5.0

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

## Sources

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

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