CVE-2019-17218
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 · uneditedAn issue was discovered on V-Zug Combi-Steam MSLQ devices before Ethernet R07 and before WLAN R05. By default, the communication to the web service is unencrypted via http. An attacker is able to intercept and sniff communication to the web service.
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 confidenceThe V-Zug Combi-Steam MSLQ devices use unencrypted HTTP communication by default for their web service, allowing attackers on the network to intercept and sniff sensitive data in transit.
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< ethernet_r07< wlan_r05CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 firmware versionAccess the device's web interface or check the device settings/system info to find the firmware version. Look for 'Ethernet' or 'WLAN' firmware version identifiers.Affected if The firmware version shown is below ethernet_r07 for Ethernet-connected units, or below wlan_r05 for WLAN-connected units.
-
Verify HTTP service is listeningFrom a system on the same network, use a browser or curl command to access http://[device-ip] (port 80). If the web interface loads over HTTP, the service is exposed.Affected if The device web interface responds on HTTP (port 80) without redirecting to HTTPS.
-
Check if HTTPS is availableAttempt to access the device over https://[device-ip] (port 443) using a browser or curl with -k flag to accept self-signed certificates.Affected if The device does not respond on HTTPS, or HTTP does not redirect to HTTPS, indicating encryption is not enabled.
-
Confirm unencrypted communication in transitUse a network packet capture tool (such as tcpdump or Wireshark) on the network segment between your client and the device. Browse the web interface and observe whether traffic is transmitted in cleartext HTTP.Affected if HTTP traffic is observed in plain text during packet capture, confirming unencrypted communication.
Your device is affected if it runs firmware versions below ethernet_r07 (for Ethernet) or below wlan_r05 (for WLAN) AND the web interface is accessible over unencrypted HTTP rather than HTTPS.
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 HTTPS/SSL encryption for the web service interface and ensure the device firmware is updated to Ethernet R07 or WLAN R05 or later.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17218 — 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-17218 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