CVE-2019-6526
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 · uneditedMoxa IKS-G6824A series Versions 4.5 and prior, EDS-405A series Version 3.8 and prior, EDS-408A series Version 3.8 and prior, and EDS-510A series Version 3.8 and prior use plaintext transmission of sensitive data, which may allow an attacker to capture sensitive data such as an administrative password.
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 confidenceMultiple Moxa industrial Ethernet switches and Ethernet servers transmit administrative credentials and other sensitive data in plaintext over the network, allowing attackers with network visibility to intercept authentication credentials via packet capture or man-in-the-middle attacks.
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<= 4.5<= 3.8<= 3.8<= 3.8CVSS 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 modelLog into the device web interface or check the physical device label to confirm the exact model number. Look for: IKS-G6824A, EDS-405A, EDS-408A, or EDS-510A.Affected if The device model matches one of the four affected models listed.
-
Check the installed firmware versionAccess the device management interface (web GUI or console) and navigate to the System Information or Firmware version page. Record the firmware version number.Affected if The firmware version is 4.5 or lower for IKS-G6824A, or 3.8 or lower for EDS-405A, EDS-408A, or EDS-510A.
-
Verify which management protocols are enabledIn the device web interface, go to the System Settings or Security settings section. Check the management protocol configuration for HTTP/HTTPS and Telnet/SSH status.Affected if HTTP (unencrypted web management) or Telnet (unencrypted CLI) is enabled while HTTPS or SSH is disabled or unavailable.
-
Capture network traffic to detect plaintext credentialsUse a network sniffer (such as Wireshark) on the management VLAN to capture traffic during login attempts. Filter for HTTP POST or Telnet traffic to observe if credentials are transmitted as cleartext.Affected if Login credentials are observed in plaintext within captured HTTP traffic or unencrypted Telnet sessions.
A defender is affected if they are running one of the listed Moxa models with firmware at or below the specified versions, and HTTP or Telnet management is enabled allowing credential interception.
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 dataEnable encrypted management protocols (HTTPS, SSH) where available, implement network segmentation to isolate management interfaces, rotate compromised credentials, and apply vendor firmware updates if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6526 — 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-2019-6526 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