dbcve.org
Eds G516e FirmwareOperating system · Moxa

CVE-2020-6991

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-24
Fix available
A fix is available. Upgrade to after 5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In Moxa EDS-G516E Series firmware, Version 5.2 or lower, weak password requirements may allow an attacker to gain access using brute force.

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 confidence

The Moxa EDS-G516E Series industrial ethernet switches running firmware version 5.2 or lower have weak password requirements that make them vulnerable to brute force attacks, allowing potential attackers to gain unauthorized administrative access to the device.

MitigationUpgrade the firmware to a version higher than 5.2 and enforce strong password policies with increased complexity and lockout mechanisms.

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
Eds G516e FirmwareOperating system
Affected:<= 5.2
Eds 510e FirmwareOperating system
Affected:<= 5.2

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
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 checks

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

  1. Identify the exact Moxa EDS model
    Check the device label on the physical hardware or log into the web management interface to confirm the model number is EDS-G516E or EDS-510E
    Affected if The model is EDS-G516E or EDS-510E series
  2. Locate the firmware version
    Access the device web interface under System > Firmware Upgrade or use the CLI command 'show version' to retrieve the currently installed firmware version
    Affected if Firmware version cannot be determined or is not visible in the interface
  3. Compare firmware to affected range
    Check if the installed firmware version is 5.2 or any version lower than 5.2
    Affected if Firmware version is 5.2 or lower (for example, 5.1, 5.0, 4.x)
  4. Verify password policy settings
    Access the device web interface under Administration > User Account or Account Settings to review the current password complexity requirements and account lockout configuration
    Affected if The device allows weak passwords (short length, no complexity requirements) or has no account lockout mechanism configured

The device is affected if it is an EDS-G516E or EDS-510E model running firmware version 5.2 or lower, which permits weak passwords vulnerable to brute force attacks.

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 a release after 5.2
Interim mitigation

Upgrade the firmware to a version higher than 5.2 and enforce strong password policies with increased complexity and lockout mechanisms.

Recommended fix Moderate confidence

Any firmware version newer than 5.2 (upgrade to the latest available stable firmware from Moxa)

  1. 1. Identify all affected Moxa EDS-G516E and EDS-510E devices in the network inventory
  2. 2. Access each device's web interface or console
  3. 3. Navigate to the firmware upgrade section (typically under System > Firmware Upgrade or Administration settings)
  4. 4. Download the latest firmware version for your device model from the official Moxa support website (www.moxa.com)
  5. 5. Upload and apply the firmware update to each affected device
  6. 6. After upgrade, verify the device is operational and accessible
  7. 7. Change all default/user passwords to comply with strong password policies (minimum 8 characters, mixed case, numbers, special characters)
  8. 8. Consider implementing account lockout policies or IP access restrictions if available
Caveat Review Moxa release notes for the target firmware version to check for any configuration or feature changes that may affect your deployment

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

Fix this in Eds G516e Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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