CVE-2019-17217
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 CSRF protection established on 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 web service lacks CSRF protection, allowing attackers to craft malicious requests that execute unintended actions when an authenticated user visits a crafted page or clicks a malicious link. This is a classic Cross-Site Request Forgery vulnerability in the embedded web interface of the kitchen appliance.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 device firmware versionAccess the device admin interface or check the device label/documentation to determine the installed firmware version. Look for version strings matching patterns like 'ethernet_rXX' or 'wlan_rXX'.Affected if The firmware version is below ethernet_r07 or below wlan_r05 (for wireless units).
-
Confirm web service is enabledAttempt to access the web interface by navigating to the device's IP address in a browser. Check if the Combi-Steam MSLQ login page loads.Affected if The web interface is accessible and responds with the appliance's login or control panel.
-
Inspect session cookie attributesLog into the web interface, open browser developer tools (F12), go to the Application/Storage tab, and examine the session cookie. Look for the 'SameSite' attribute value.Affected if The session cookie has no SameSite attribute set, or it is set to 'None' without the Secure flag.
-
Check for CSRF token presenceSubmit a state-changing request (such as changing a setting or temperature). Intercept the request using a proxy or developer tools and examine if a CSRF token, anti-CSRF token, or similar parameter is included in the request body or headers.Affected if No CSRF token or anti-CSRF parameter is present in POST/PUT/DELETE requests that modify device state.
You are affected if your V-Zug Combi-Steam MSLQ firmware is below ethernet_r07 (or below wlan_r05 for wireless) AND the web interface is accessible without CSRF token validation or proper SameSite cookie protections.
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 dataImplement CSRF tokens or SameSite cookie attributes on all state-changing web service endpoints to validate request origin and prevent forged requests from untrusted sources.
- Consultation6.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 $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17217 — 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-17217 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