CVE-2019-6577
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 · uneditedA vulnerability has been identified in SIMATIC HMI Comfort Panels 4" - 22" (All versions < V15.1 Update 1), SIMATIC HMI Comfort Outdoor Panels 7" & 15" (All versions < V15.1 Update 1), SIMATIC HMI KTP Mobile Panels KTP400F, KTP700, KTP700F, KTP900 und KTP900F (All versions < V15.1 Update 1), SIMATIC WinCC Runtime Advanced (All versions < V15.1 Update 1), SIMATIC WinCC Runtime Professional (All versions < V15.1 Update 1), SIMATIC WinCC (TIA Portal) (All versions < V15.1 Update 1), SIMATIC HMI Classic Devices (TP/MP/OP/MP Mobile Panel) (All versions). The integrated web server could allow Cross-Site Scripting (XSS) attacks if an attacker is able to modify particular parts of the device configuration via SNMP. The security vulnerability could be exploited by an attacker with network access to the affected system. Successful exploitation requires system privileges and user interaction. An attacker could use the vulnerability to compromise confidentiality and the integrity of the affected system. At the stage of publishing this security advisory no public exploitation is known.
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 integrated web server in SIMATIC HMI Comfort Panels, Mobile Panels, WinCC Runtime Advanced, WinCC Runtime Professional, and WinCC (TIA Portal) contains a stored Cross-Site Scripting (XSS) vulnerability. An attacker with network access and system privileges can inject malicious scripts into device configuration via SNMP, which then executes when users interact with the web server interface.
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< 15.1< 15.1< 15.1< 15.1< 15.1< 15.1< 15.1< 15.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 your product and versionAccess the device web interface or use TIA Portal to determine the exact product model and firmware/software version. For HMI panels, check System Diagnostics > Device Info. For WinCC, check the project properties or About dialog.Affected if The version is older than V15.1 (for HMI panels: any firmware < 15.1; for WinCC TIA Portal: any version < 15.1)
-
Verify the integrated web server is enabledCheck the device or project settings to confirm the web server functionality is active. On HMI panels, navigate to Runtime Settings > Web Server. In TIA Portal, check the HMI device properties for web server configuration.Affected if The web server is enabled and running, making the stored XSS exploitable through user interaction with the interface
-
Confirm SNMP is accessibleCheck the SNMP settings on the device or in the project. Verify whether SNMP community strings are configured and whether SNMP access is permitted from network segments where attackers could reach the device.Affected if SNMP is enabled and accessible from untrusted networks, which is the injection vector for the malicious scripts
-
Inspect device configuration for suspicious contentReview the SNMP configuration and device parameters that could contain user-supplied data. Check if any Device ID, System Name, or other SNMP-managed fields contain unexpected characters or script tags that may indicate prior exploitation.Affected if Unexpected script tags or encoded JavaScript are present in SNMP-configurable fields or device description parameters
You are affected if your HMI panel firmware or WinCC TIA Portal version is below V15.1 AND the integrated web server is enabled, as this creates the conditions for the stored XSS to execute when users access the web interface.
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 data15.1
Update all affected SIMATIC HMI and WinCC products to V15.1 Update 1 or later. If immediate patching is not feasible, restrict SNMP access to trusted management stations and implement network segmentation to limit exposure.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6577 — 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-6577 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