# CVE-2024-11303: Path Traversal

> An attacker can exploit a path traversal vulnerability in the Korenix JetPort 5601 to access restricted directories and read sensitive files.

- **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:** 18 Nov 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-qj8p-7c2x-55jf

## What is CVE-2024-11303?

CVE-2024-11303 is a high-severity path traversal vulnerability in Korenix JetPort 5601, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The pathname of the root directory to a Restricted Directory ('Path Traversal') vulnerability in Korenix JetPort 5601 allows Path Traversal.This issue affects JetPort 5601: through 1.2.

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

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


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

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

## Is CVE-2024-11303 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11303 exists.

Public exploit code:

- Korenix JetPort 5601v3 - Path Traversal (nuclei): http/cves/2024/CVE-2024-11303.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11303 is a high-severity path traversal vulnerability in Korenix JetPort 5601, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11303 exists.

Affected product: Korenix JetPort 5601. 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-11303/ (Markdown: https://insights.sbomify.com/CVE-2024-11303/index.md)
```

## Sources

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

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