CVE-2019-17215
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. There is no bruteforce protection (e.g., lockout) established. An attacker might be able to bruteforce the password to authenticate on 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 confidenceV-Zug Combi-Steam MSLQ cooking devices lack bruteforce protection, allowing attackers to repeatedly guess passwords without account lockout or throttling. This enables automated credential stuffing attacks to gain unauthorized administrative access to the device.
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
- 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.
-
Confirm device model is V-Zug Combi-Steam MSLQAccess the device web interface or check the physical device label to verify the exact model number matches the V-Zug Combi-Steam MSLQ cooking device.Affected if The device is a V-Zug Combi-Steam MSLQ model.
-
Identify installed firmware versionLog into the device admin interface and navigate to the System or Firmware section to view the currently installed firmware version. The version should display as either 'ethernet_rXX' or 'wlan_rXX' format.Affected if The firmware version displays as ethernet_r07 or lower, or wlan_r05 or lower.
-
Compare firmware version against affected rangesCompare your identified firmware version number to the affected ranges: ethernet versions below r07 and wlan versions below r05. Note that ethernet and wlan refer to different connectivity modules.Affected if The firmware version is below ethernet_r07 OR below wlan_r05.
-
Verify web admin interface is network-accessibleAttempt to access the device web interface from a network location or check firewall rules to determine if the admin portal (typically on ports 80/443 or custom ports) is reachable from network segments beyond the local device.Affected if The device admin interface is accessible from network segments beyond the immediate local network.
-
Check for account lockout behaviorAttempt multiple failed login attempts (using a test account or observing login behavior documentation) to observe whether the device implements account lockout, throttling, or rate-limiting after repeated failed authentication attempts.Affected if The device does not lock out accounts or throttle login attempts after multiple failed password attempts.
The device is affected if it is a V-Zug Combi-Steam MSLQ running firmware below ethernet_r07 or wlan_r05, and the admin interface is network-accessible without brute force protection in place.
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 dataUpdate firmware to Ethernet R07 or WLAN R05 and later to receive vendor-provided bruteforce protection. Additionally, isolate device on restricted network segments and enforce strong passwords to reduce attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17215 — 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-17215 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