dbcve.org
Edr G903 FirmwareOperating system · Moxa

CVE-2023-4452

HIGH · 7.5 CVSS v3.1 Published 2023-11-01
Fix available
A fix is available. Upgrade to 5.7.21 / 5.12.29 or later.
See remediation →
84/100
Remediation priority · High
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
A vulnerability has been identified in the EDR-810, EDR-G902, and EDR-G903 Series, making them vulnerable to the denial-of-service vulnerability. This vulnerability stems from insufficient input validation in the URI, potentially enabling malicious users to trigger the device reboot.

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 confidence

The EDR-810, EDR-G902, and EDR-G903 Series industrial Ethernet devices contain an input validation flaw in their URI handling logic. Attackers can send specially crafted HTTP requests with malicious URIs that cause the device to reboot, resulting in denial of service.

MitigationApply vendor-supplied firmware patches when available; until then, restrict network access to the device's web management interface using firewall rules or network segmentation to limit exposure to untrusted networks.

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
Edr G903 FirmwareOperating system
Affected:< 5.7.21
Edr G903 T FirmwareOperating system
Affected:< 5.7.21
Edr G902 FirmwareOperating system
Affected:< 5.7.21
Edr G902 T FirmwareOperating system
Affected:< 5.7.21
Edr 810 Vpn 2gsfp FirmwareOperating system
Affected:< 5.12.29
Edr 810 Vpn 2gsfp T FirmwareOperating system
Affected:< 5.12.29
Edr 810 2gsfp FirmwareOperating system
Affected:< 5.12.29
Edr 810 2gsfp T FirmwareOperating system
Affected:< 5.12.29

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
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify the exact device model
    Log into the device console or web interface and locate the model name displayed in the system information or device status page. Confirm whether it is an EDR-810, EDR-G902, EDR-G903, or one of their T variants (e.g., EDR-810 2GSFP T, EDR-G903 T).
    Affected if The device model matches any of the following: EDR-810, EDR-G902, EDR-G903, or their T variants (EDR-810 Vpn 2gsfp T, EDR-810 2gsfp T, EDR-G902 T, EDR-G903 T).
  2. Check the installed firmware version
    Access the device web interface and navigate to System Settings or System Information to view the firmware version. Alternatively, use the device console or CLI to run a version command if available.
    Affected if The firmware version is below 5.7.21 for EDR-G902 or EDR-G903 variants, or below 5.12.29 for EDR-810 variants.
  3. Verify the web management interface is enabled
    In the device web interface, go to Network Settings or Service Settings and confirm whether the HTTP/HTTPS web management service is turned on.
    Affected if The web management interface (HTTP port 80 or HTTPS port 443) is enabled and accessible.
  4. Check network exposure of the web interface
    Review firewall rules, VLAN configurations, or network ACLs to determine if the device web management ports (80/443) are exposed to untrusted networks or the public internet.
    Affected if The web management interface is reachable from networks outside the trusted management zone.

A user is affected if they have an EDR-810, EDR-G902, or EDR-G903 device (or T variants) running firmware below 5.7.21 (for G902/G903) or below 5.12.29 (for EDR-810), with the web management interface enabled and accessible from their network.

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.

dbcve · scoped
Upgrade available Upgrade to 5.7.21 / 5.12.29 or later
Fixed in 5.7.215.12.29
Interim mitigation

Apply vendor-supplied firmware patches when available; until then, restrict network access to the device's web management interface using firewall rules or network segmentation to limit exposure to untrusted networks.

Recommended fix Moderate confidence

Firmware 5.7.21 or higher for EDR-G902/G903 series; Firmware 5.12.29 or higher for EDR-810 series

  1. 1. Identify the exact model number of the Moxa EDR device (EDR-810, EDR-G902, or EDR-G903 series).
  2. 2. Visit the official Moxa support website at www.moxa.com to locate the firmware download section.
  3. 3. Download the firmware version 5.7.21 or higher for EDR-G902/G903 series devices.
  4. 4. Download the firmware version 5.12.29 or higher for EDR-810 series devices.
  5. 5. Consult the device firmware upgrade manual for proper upload procedures.
  6. 6. Upload the new firmware to the device through the web interface or management console.
  7. 7. Verify the firmware version after upgrade to confirm successful installation.
  8. 8. Reboot the device if not automatically performed and verify normal operation.
Caveat Review Moxa release notes for any configuration or feature changes between versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Edr G903 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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