CVE-2024-0387
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 · uneditedThe EDS-4000/G4000 Series prior to version 3.2 includes IP forwarding capabilities that users cannot deactivate. An attacker may be able to send requests to the product and have it forwarded to the target. An attacker can bypass access controls or hide the source of malicious requests.
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 confidenceThe EDS-4000/G4000 Series network devices contain a non-disableable IP forwarding feature prior to firmware version 3.2. This allows an attacker to route traffic through the compromised device, effectively using it as a proxy to bypass network access controls and mask the origin of malicious requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.2<= 3.2<= 3.2<= 3.2<= 3.2<= 3.2<= 3.2CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 is in the affected seriesAccess the device web interface, CLI, or use SNMP to identify the exact model number. Verify it is one of: EDS-4008, EDS-4009, EDS-4012, EDS-4014, EDS-G4008, EDS-G4012, or EDS-G4014.Affected if The device model matches one of the listed affected models.
-
Check installed firmware versionAccess the device web interface (System > Firmware or About page), CLI (show version or show system-info), or SNMP to retrieve the current firmware version.Affected if The firmware version is 3.2 or lower.
-
Verify IP forwarding is enabledAccess the device web interface under Network > IP Forwarding or Routing > IP Forwarding settings. Check the current status of the IP forwarding feature.Affected if IP forwarding is currently enabled on the device.
The device is affected if it is an EDS-4000 or G4000 series model running firmware version 3.2 or lower with IP forwarding enabled.
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.
dbcve · scopedUpdate firmware to version 3.2 or later, which reportedly adds the ability to deactivate IP forwarding. If immediate patching is not feasible, implement network segmentation and firewall rules to restrict the device from forwarding unauthorized traffic.
Firmware version 3.2 or later
- 1. Identify the exact model number of your EDS-4000/G4000 series device (e.g., EDS-4008, EDS-G4012)
- 2. Access the device's web interface or console
- 3. Navigate to the firmware upgrade section
- 4. Download the latest firmware version from Moxa's official support website (www.moxa.com)
- 5. Upload and apply firmware version 3.2 or later
- 6. After upgrade, verify that IP forwarding can now be deactivated in the device settings
- 7. If IP forwarding is not needed, disable it to mitigate the vulnerability
- 8. Verify the device is functioning correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0387 — 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-0387 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