# CVE-2024-2461: Path traversal in FOX61x

> Attackers can traverse the file system to access restricted files or directories in Hitachi Energy ICS products.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-89q4-gfxm-xg78

## What is CVE-2024-2461?

CVE-2024-2461 is a medium-severity path traversal vulnerability in Hitachi Energy FOX61x, published on 11 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

If exploited an attacker could traverse the file system to access 
files or directories that would otherwise be inaccessible

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2024-2461?


## How do I fix CVE-2024-2461?

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

## Is CVE-2024-2461 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2461 and fix it if it is affected.

What it is: CVE-2024-2461 is a medium-severity path traversal vulnerability in Hitachi Energy FOX61x, published on 11 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2461 in the wild and no public exploit code.

Affected product: Hitachi Energy FOX61x. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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