dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022.
Simatic Cp 1543 1 FirmwareOperating system · Siemens

CVE-2016-8562

HIGH · 7.5 CVSS v3.1 Published 2016-11-18
Fix available
A fix is available. Upgrade to 2.0.28 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable Zero-click Patch available

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 · unedited
A vulnerability has been identified in SIMATIC CP 1543-1 (All versions < V2.0.28), SIPLUS NET CP 1543-1 (All versions < V2.0.28). Under special conditions it was possible to write SNMP variables on port 161/udp which should be read-only and should only be configured with TIA-Portal. A write to these variables could reduce the availability or cause a denial-of-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 confidence

The SIMATIC CP 1543-1 and SIPLUS NET CP 1543-1 devices allow unauthorized write access to SNMP variables on port 161/UDP that should be read-only and only configurable through TIA-Portal. An unauthenticated attacker can write to these SNMP variables, potentially causing denial-of-service or reducing system availability.

MitigationUpgrade firmware to version V2.0.28 or later. Additionally, restrict network access to port 161/UDP through firewalls or network segmentation to limit exposure to untrusted networks.

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
Simatic Cp 1543 1 FirmwareOperating system
Affected:< 2.0.28
Siplus Net Cp 1543 1 FirmwareOperating system
Affected:< 2.0.28

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or use SNMP to query the sysDescr or device identification OIDs (1.3.6.1.2.1.1.1, 1.3.6.1.2.1.1.2) to confirm the device is a SIMATIC CP 1543-1 or SIPLUS NET CP 1543-1
    Affected if The device model is SIMATIC CP 1543-1 or SIPLUS NET CP 1543-1
  2. Check the firmware version
    Access the device web interface or use SNMP to query the firmware version OID. Compare the installed version against the affected range of versions prior to 2.0.28
    Affected if The firmware version is lower than 2.0.28
  3. Verify SNMP is enabled
    Confirm that SNMP is enabled on the device by checking the SNMP service status in the device configuration or by attempting an SNMP query to port 161/UDP
    Affected if SNMP is enabled and responding on port 161/UDP
  4. Confirm SNMP write access exposure
    Attempt an SNMP SET request to a read-only OID (such as system.sysContact or system.sysLocation) from an untrusted network segment without authentication
    Affected if The SNMP SET request succeeds without authentication, indicating write access is exposed

The device is affected if it is a SIMATIC CP 1543-1 or SIPLUS NET CP 1543-1 with firmware version prior to 2.0.28 and SNMP is accessible on port 161/UDP with unauthenticated write capability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.0.28 or later
Fixed in 2.0.28
Vendor patch www.siemens.com →
Interim mitigation

Upgrade firmware to version V2.0.28 or later. Additionally, restrict network access to port 161/UDP through firewalls or network segmentation to limit exposure to untrusted networks.

Recommended fix High confidence

Firmware V2.0.28 or later for SIMATIC CP 1543-1 and SIPLUS NET CP 1543-1

  1. 1. Identify the exact model and current firmware version of the affected SIMATIC CP 1543-1 or SIPLUS NET CP 1543-1 device
  2. 2. Download firmware version V2.0.28 or later from the official Siemens support portal (www.siemens.com) or cert-portal.siemens.com
  3. 3. Backup the current device configuration before performing the firmware update
  4. 4. Upload the new firmware V2.0.28 or later to the device using the TIA-Portal or web-based management interface
  5. 5. After firmware installation, verify the device is running the updated version
  6. 6. Confirm that SNMP write access to read-only variables is now properly restricted
Caveat Review release notes for V2.0.28 to check for any changes to SNMP configuration or other settings that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Simatic Cp 1543 1 Firmware Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,960
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-8562 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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