# CVE-2024-9301: Path traversal in E2Nest

> Attackers can exploit a path traversal flaw in the E2Nest library to read or modify arbitrary files on the system.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2024
- **Updated:** 27 Sep 2024

## What is CVE-2024-9301?

CVE-2024-9301 is a high-severity path traversal vulnerability in Netflix E2Nest, published on 27 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal issue in E2Nest prior to commit 8a41948e553c89c56b14410c6ed395e9cfb9250a

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Netflix E2nest.

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

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

## Is CVE-2024-9301 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9301 is a high-severity path traversal vulnerability in Netflix E2Nest, published on 27 Sep 2024. 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-2024-9301 in the wild and no public exploit code.

Affected product: Netflix E2Nest. 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-9301/ (Markdown: https://insights.sbomify.com/CVE-2024-9301/index.md)
```

## Sources

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

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