dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-7395

CRITICAL · 9.3 CVSS v4.0 Published 2024-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Korenix JetPort 5601v3 serial-to-Ethernet device contains an authentication bypass vulnerability in versions through 1.2. An attacker can access device functionality without providing any password, effectively bypassing the authentication mechanism entirely. This critical flaw enables unauthorized remote access to configure or manipulate the device.

MitigationIf a patched firmware version is available from Korenix, apply it immediately. Otherwise, isolate the affected device behind a firewall, restrict network access to trusted IPs only, and monitor for unauthorized access attempts. Consider replacing the device if no patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or check the device label/marketing materials to confirm it is a Korenix JetPort 5601v3 serial-to-Ethernet device.
    Affected if The device is NOT a Korenix JetPort 5601v3, then it is not affected by this specific CVE.
  2. Determine the installed firmware version
    Log into the device web interface and navigate to the System or Firmware information page to retrieve the current firmware version number.
    Affected if The firmware version is 1.2 or lower (versions through 1.2 are affected).
  3. Verify web interface authentication behavior
    Open a fresh browser session to the device IP address without providing any credentials. Attempt to access the main configuration pages directly without logging in.
    Affected if The device allows full or partial access to configuration pages without requiring any password, indicating the authentication bypass is present.
  4. Check for unexpected session tokens
    Inspect browser cookies or session identifiers after accessing the device without login. Compare to behavior when authentication is properly enforced.
    Affected if A valid session is established without any authentication exchange, confirming the bypass.

You are affected if you have a Korenix JetPort 5601v3 device running firmware version 1.2 or lower, and the web interface grants access to configuration functions without prompting for any password.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If a patched firmware version is available from Korenix, apply it immediately. Otherwise, isolate the affected device behind a firewall, restrict network access to trusted IPs only, and monitor for unauthorized access attempts. Consider replacing the device if no patch is available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7395 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data