CVE-2019-6518
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 and EDS store plaintext passwords, which may allow sensitive information to be read by someone with access to 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 · moderate confidenceMoxa IKS and EDS industrial network switches store user credentials in plaintext within device storage or configuration files, allowing anyone with physical or administrative access to retrieve actual passwords rather than hashed values.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 device model and firmware versionAccess the device web interface, console, or SNMP to retrieve the exact model number (IKS G6824A, EDS 405A, EDS 408A, or EDS 510A) and current firmware version. This is typically found under System > Device Information or similar admin section.Affected if The firmware version is 4.5 or lower for IKS G6824A, or 3.8 or lower for EDS models.
-
Export device configuration fileUse the device admin interface to export the configuration file. This is usually found under Configuration > Backup/Restore or System > Configuration > Export. The file is typically in .cfg or .conf format.Affected if A configuration file can be exported from the device.
-
Inspect configuration for plaintext credentialsOpen the exported configuration file with a text editor and search for password-related fields (such as 'password', 'pwd', 'user', or 'admin'). Examine whether the values appear as plaintext strings rather than hashed or encrypted values.Affected if Password fields in the configuration contain readable text that matches actual login passwords, indicating plaintext storage.
-
Check device storage for credential filesIf you have physical or administrative access to the device filesystem (via SD card slot, FTP, or TFTP backup), examine any stored user databases or credential files for plaintext password entries.Affected if User database or credential files on the device storage contain passwords in readable plaintext format.
A user is affected if they have a Moxa IKS G6824A device with firmware <= 4.5 or an EDS 405A/408A/510A device with firmware <= 3.8, and their configuration files or device storage contain plaintext (unhashed) password values.
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 dataApply vendor firmware updates when available; until then, restrict physical access to devices, limit administrative accounts, and consider network segmentation to reduce exposure of plaintext credentials.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.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 $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6518 — 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-6518 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