# CVE-2024-7395: Insufficient Authentication

> Attackers can bypass authentication to access device functionality without a password on Korenix JetPort 5601v3 switches.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 5 Aug 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-72x9-mq39-cp23

## What is CVE-2024-7395?

CVE-2024-7395 is a critical authentication bypass vulnerability in Korenix JetPort 5601v3, published on 5 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability in Korenix JetPort 5601v3 allows an attacker to access functionality on the device without specifying a password.This issue affects JetPort 5601v3: through 1.2.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2024-7395 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7395 is a critical authentication bypass vulnerability in Korenix JetPort 5601v3, published on 5 Aug 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-7395 in the wild and no public exploit code.

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

## Sources

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

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