CVE-2019-6568
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 · uneditedThe webserver of the affected devices contains a vulnerability that may lead to a denial of service condition. An attacker may cause a denial of service situation which leads to a restart of the webserver of the affected device. The security vulnerability could be exploited by an attacker with network access to the affected systems. Successful exploitation requires no system privileges and no user interaction. An attacker could use the vulnerability to compromise availability of 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 confidenceThe affected devices contain a vulnerability in their webserver component that allows an unauthenticated remote attacker to trigger a denial of service condition. Successful exploitation causes the webserver to restart, disrupting device availability. The attack requires only network access to the targeted device with no privileges or user interaction needed.
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 dataall versionsall versions< 1.1.0all versionsall versionsall versions< 2.1.6< 2.7CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the device modelLocate the physical device labeling or access the device's management interface to confirm the exact model number (e.g., Cp1604, Cp1616, Simatic RF185C, Cp343-1 Advanced, Cp443-1, ET 200 SP Open Controller)Affected if The device model matches one of the affected products listed in the CVE
-
Determine the firmware versionAccess the device's web-based management interface or use the vendor's configuration software to retrieve the installed firmware versionAffected if The installed firmware version falls within the affected range: all versions for Cp1604, Cp1616, Cp343-1 Advanced, Cp443-1, Cp443-1 Advanced; versions below 1.1.0 for RF185C; versions below 2.1.6 for ET 200 SP CPU 1515SP PC; versions below 2.7 for ET 200 SP CPU 1515SP PC2
-
Verify the webserver component is enabledCheck the device configuration settings or management interface for webserver/web services status. Confirm that the HTTP or HTTPS webserver interface is actively running and accessibleAffected if The webserver component is enabled and accessible on the network, as the vulnerability resides in this component and exploitation requires network access to it
-
Assess network exposure of the webserverReview network firewall rules, access control lists, or network segmentation configurations to determine if the device webserver interface is reachable from untrusted networksAffected if The webserver is exposed to untrusted network segments or the internet, enabling an unauthenticated remote attacker to reach the vulnerable component
The environment is affected if the device is one of the listed Siemens models with a vulnerable firmware version and the webserver component is network-accessible.
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 data1.1.02.1.62.7
Restrict network access to the device's webserver interface through firewall rules or network segmentation. If vendor patches become available, apply them promptly. Consider implementing rate limiting or intrusion detection as compensating controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6568 — 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-6568 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