CVE-2020-14511
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 · uneditedMalicious operation of the crafted web browser cookie may cause a stack-based buffer overflow in the system web server on the EDR-G902 and EDR-G903 Series Routers (versions prior to 5.4).
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 confidenceA stack-based buffer overflow vulnerability exists in the system web server of EDR-G902 and EDR-G903 Series industrial routers running firmware versions prior to 5.4. The vulnerability is triggered by sending a maliciously crafted web browser cookie, potentially allowing remote code execution with high severity impact.
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.4<= 5.4<= 5.4<= 5.4CVSS 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 device modelAccess the router web interface or check the physical device label to confirm it is an EDR-G902 or EDR-G903 series industrial router.Affected if The device model is Moxa EDR-G902 or EDR-G903.
-
Check the installed firmware versionLog into the router web interface and navigate to the System > Firmware or Status page to view the current firmware version. Alternatively, use the command line interface and run the 'show version' or 'system info' command.Affected if The firmware version is 5.4 or earlier (e.g., 5.3.x, 5.2.x, etc.).
-
Verify the web server is enabledIn the router web interface, go to Network Settings > HTTP/HTTPS or System Settings > Services to confirm the web server (HTTP or HTTPS) is currently enabled.Affected if The web server service is enabled and accessible.
-
Check if remote web access is permittedIn the router web interface, review the Access Control or Remote Management settings to determine whether remote (WAN) access to the web management interface is allowed.Affected if Remote access to the web interface is permitted, making the vulnerability exploitable from external networks.
The device is affected if it is an EDR-G902 or EDR-G903 router running firmware version 5.4 or earlier with the web server enabled and accessible remotely.
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 · scopedUpgrade the router firmware to version 5.4 or later to patch the vulnerability. If immediate patching is not feasible, restrict network access to the web management interface using firewall rules or disable remote web administration.
Firmware version 5.4 or later (latest available version recommended)
- 1. Identify the current firmware version of the EDR-G902 or EDR-G903 Series Router by accessing the device web interface or using the device's management console
- 2. Download the latest firmware version from the official vendor (Advantech/B+B SmartWorx) support website for your specific EDR-G902 or EDR-G903 model
- 3. Access the router's web-based management interface using administrator credentials
- 4. Navigate to the firmware upgrade section (typically under System > Maintenance > Firmware Upgrade or similar path)
- 5. Upload the downloaded firmware file and initiate the upgrade process
- 6. Wait for the upgrade to complete - do not power off the device during this process
- 7. After reboot, verify the new firmware version is installed and the device is functioning normally
- 8. Test that the web server functionality is working properly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.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 $3,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14511 — 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-14511 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