dbcve.org
Iks G6824a FirmwareOperating system · Moxa

CVE-2019-6563

CRITICAL · 9.8 CVSS v3.1 Published 2019-03-05
Fix available
A fix is available. Upgrade to after 4.5 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
Moxa IKS and EDS generate a predictable cookie calculated with an MD5 hash, allowing an attacker to capture the administrator's password, which could lead to a full compromise of the device.

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

Moxa IKS and EDS industrial network devices generate authentication cookies using a predictable algorithm based on MD5 hashing. The weak cryptographic implementation allows attackers to reverse-engineer or brute-force the cookie generation logic, enabling session hijacking and capture of plaintext administrator passwords.

MitigationApply vendor-supplied firmware patches when available. In the interim, restrict network access to management interfaces via firewall rules or VPN, and monitor for unauthorized access attempts.

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
Iks G6824a FirmwareOperating system
Affected:<= 4.5
Eds 405a FirmwareOperating system
Affected:<= 3.8
Eds 408a FirmwareOperating system
Affected:<= 3.8
Eds 510a FirmwareOperating system
Affected:<= 3.8

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 Moxa device model
    Access the device web interface or use network discovery to determine if the device is a Moxa IKS G6824a, EDS 405a, EDS 408a, or EDS 510a. Check the device information or label for the exact model number.
    Affected if The device model is one of: IKS G6824a, EDS 405a, EDS 408a, or EDS 510a.
  2. Check the installed firmware version
    Log into the device web interface and navigate to System Settings > Firmware Information, or use the device console/CLI to run the command that displays firmware version (typically 'show version' or accessible via the web GUI system info page).
    Affected if The firmware version is at or below 4.5 for IKS G6824a, or at or below 3.8 for EDS 405a, EDS 408a, or EDS 510a.
  3. Verify web-based management interface is enabled
    Check the device configuration under Network Settings or System Settings to confirm the HTTP/HTTPS web management interface is enabled and accessible.
    Affected if The web management interface is enabled and exposed on the network.
  4. Inspect authentication cookie behavior
    Attempt to log in via the web interface and capture the session cookie using browser developer tools or a proxy. Observe if cookies appear to be static or predictable across multiple sessions, or use a packet capture to examine cookie values.
    Affected if Session cookies are generated with predictable patterns or remain constant between logins.

The environment is affected if the device is a vulnerable Moxa model (IKS G6824a, EDS 405a, EDS 408a, or EDS 510a) running firmware at or below the affected version, and the web management interface with cookie-based authentication is enabled.

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 4.5
Interim mitigation

Apply vendor-supplied firmware patches when available. In the interim, restrict network access to management interfaces via firewall rules or VPN, and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

IKS G6824a: upgrade to firmware >= 4.6; EDS 405a/408a/510a: upgrade to firmware >= 3.9

  1. Identify the exact model number (Iks G6824a, Eds 405a, Eds 408a, or Eds 510a) from the affected device
  2. Visit the official Moxa support website (www.moxa.com) and navigate to the product's download/firmware section
  3. Locate the firmware version for your specific device model
  4. Download the latest available firmware version - for IKS G6824a this should be version 4.6 or higher; for EDS models (405a, 408a, 510a) this should be version 3.9 or higher
  5. Review the firmware release notes to confirm the security fix for CVE-2019-6563 is included
  6. Follow Moxa's standard firmware upgrade procedure - typically via the web interface or dedicated upgrade tool
  7. After upgrading, verify the new firmware version is installed and test that authentication functions correctly
Caveat Review release notes for any changes to configuration or functionality before upgrading production devices

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

Fix this in Iks G6824a Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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