CVE-2024-57790
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 · uneditedIXON B.V. IXrouter IX2400 (Industrial Edge Gateway) v3.0 was discovered to contain hardcoded root credentials stored in the non-volatile flash memory. This vulnerability allows physically proximate attackers to gain root access via UART or SSH.
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 · high confidenceThe IXON IXrouter IX2400 industrial edge gateway v3.0 contains hardcoded root credentials embedded in non-volatile flash memory. Physically proximate attackers with access to the device can extract these credentials and gain root-level access via UART console or SSH.
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
- Physical
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model and firmware versionAccess the device admin interface or check the boot log via UART/SSH and identify the exact model number and firmware version. Look for 'IXON IXrouter IX2400' and version 'v3.0'.Affected if The device is an IXON IXrouter IX2400 running firmware version 3.0 (or any version within the v3.0 release line).
-
Verify UART console is accessiblePhysically inspect the device PCB for exposed UART pins (typically 3-4 pins in a row: TX, RX, GND, VCC). Check if the UART console is enabled in the device configuration or if boot logs are accessible without authentication.Affected if UART pins are exposed on the PCB or the UART console is accessible without authentication, allowing a physically proximate attacker to interact with the boot process.
-
Check SSH service statusFrom a networked host, attempt to connect to the device SSH service (port 22 typically) using a network scanner or telnet/ssh client. Verify if SSH is enabled and responding.Affected if SSH is enabled and reachable on the device, providing a potential access vector once hardcoded credentials are obtained.
-
Assess physical access controlsEvaluate the physical security of the device deployment environment. Determine if the device is located in a secured area with restricted access, or if it is in a publicly accessible location where a physically proximate attacker could gain device access.Affected if The device is deployed in an area without adequate physical access controls, allowing an attacker to physically access the device, its UART ports, or its flash memory.
A user is affected if they operate an IXON IXrouter IX2400 v3.0 gateway where the UART console or SSH service is accessible and the device lacks sufficient physical access controls to prevent a physically proximate attacker from extracting hardcoded credentials from flash memory.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace hardcoded credentials with unique, securely-managed credentials; disable unauthenticated UART console access; apply firmware updates if available that remove hardcoded credentials; restrict physical access to the device.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57790 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-57790 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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