dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-7397

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
Improper filering of special characters result in a command ('command injection') vulnerability in Korenix JetPort 5601v3.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

Command injection vulnerability in Korenix JetPort 5601v3 serial-to-Ethernet gateway allows remote attackers to execute arbitrary OS commands via improper filtering of special characters in user-supplied input. The device web interface or management API fails to sanitize meta-characters before passing them to system shell calls, enabling complete system compromise with network-level access.

MitigationApply vendor firmware patch if available; otherwise isolate device behind firewall with restricted access, disable remote management interfaces if not required, and monitor for unauthorized access attempts.

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 device model
    Access the device web interface, check the system status page, or use network discovery to confirm the exact model is JetPort 5601v3
    Affected if Device is a Korenix JetPort 5601v3 serial-to-Ethernet gateway
  2. Verify web management interface is enabled
    Attempt to access the device HTTP/HTTPS management port (typically ports 80/443 or vendor-default) from an authorized network segment
    Affected if Web interface responds and accepts user authentication
  3. Check management API accessibility
    Probe the device for REST API endpoints or management service ports used for device configuration
    Affected if API endpoints are reachable and accept input
  4. Confirm network exposure of management interface
    Review firewall rules or network ACLs to determine if the management interface is accessible from outside the local management network
    Affected if Management interface is exposed to untrusted networks or the internet
  5. Locate firmware version
    In the web interface, navigate to System > Firmware/Version or check the device status page for the installed firmware build number
    Affected if Unable to determine firmware version OR firmware version predates any available patch

You are affected if you have a Korenix JetPort 5601v3 gateway with its web interface or management API accessible on the network, since the vulnerability is triggered through user input processed by these interfaces.

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

Apply vendor firmware patch if available; otherwise isolate device behind firewall with restricted access, disable remote management interfaces if not required, and monitor for unauthorized access attempts.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7397 — 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-7397 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