CVE-2020-28144
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 · uneditedCertain Moxa Inc products are affected by an improper restriction of operations in EDR-G903 Series Firmware Version 5.5 or lower, EDR-G902 Series Firmware Version 5.5 or lower, and EDR-810 Series Firmware Version 5.6 or lower. Crafted requests sent to the device may allow remote arbitrary code execution.
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 confidenceMoxa EDR-G903, EDR-G902, and EDR-810 Series security appliances contain an improper restriction of operations vulnerability allowing remote attackers to execute arbitrary code via crafted HTTP requests. The flaw affects firmware versions 5.5 and lower for the G903/G902 series and 5.6 and lower for the EDR-810, enabling complete system compromise without authentication.
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<= 5.5<= 5.5<= 5.5<= 5.5<= 5.6<= 5.6<= 5.6<= 5.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify the exact EDR modelLocate the device model number on the physical unit label or check via the web management interface under System Information or Device StatusAffected if Model is EDR-G903, EDR-G902, or EDR-810 series
-
Check the installed firmware versionAccess the web management interface and navigate to System > Firmware/Version or use the console and run the firmware version commandAffected if Firmware version is 5.5 or lower for EDR-G903/G902 series, or 5.6 or lower for EDR-810 series
-
Verify if HTTP web management is enabledCheck the device network configuration via the web interface under Network > Services or System > Access Settings to see if HTTP/HTTPS management is activeAffected if HTTP web management interface is enabled and accessible
-
Confirm network exposure of management interfaceReview firewall rules, ACLs, or network segmentation to determine if the web management port (80/443) is reachable from untrusted networksAffected if The HTTP management interface is exposed to the internet or untrusted networks
You are affected if you have an EDR-G903/G902 device on firmware 5.5 or lower, or an EDR-810 device on firmware 5.6 or lower, with the web management interface enabled and reachable.
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 dataUpgrade firmware to versions higher than 5.5 for EDR-G903/G902 series and higher than 5.6 for EDR-810 series. If patching is not immediately possible, restrict network access to management interfaces using firewalls or ACLs and monitor for suspicious crafted requests.
- Consultation6.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28144 — 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-2020-28144 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