Vulnerability report

Exploited in the wild Confirmed confidence In CISA KEV

CVE-2016-8562

SIMATIC CP 1543-1

Siemens / SIMATIC CP 1543-1

Watch CVE-2016-8562 Browse KEV feed
Severity
CVSS 7.5 · High
Confidence
Confirmed
Exploit status
Exploited in the wild
EPSS
3.6%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2016-8562 is a vulnerability affecting Siemens SIMATIC CP 1543-1, SIPLUS NET CP 1543-1. A vulnerability has been identified in SIMATIC CP 1543-1 (All versions < V2.0.28), SIPLUS NET CP 1543-1 (All versions <...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV.

Who is affected?

Siemens / SIMATIC CP 1543-1.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

SIMATIC CP 1543-1

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.

Published
18 Nov 2016
Exploitation Reported
03 Mar 2022
Attack vector
Remote
Complexity
High
Privileges
Low
User interaction
None

Tags

cisa nessus_scanner

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CISA

Recorded 03 Mar 2022

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CISA First 2022-03-03 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

7.5 High

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

3.6%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

All CVSS Scores

CVSS v3.1 7.5 High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS v2.0 3.5 Low

AV:N/AC:M/Au:S/C:N/I:N/A:P

Timeline

From disclosure to observed exploitation

  1. 00:00 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  2. 21:00 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2016-8562

Sample API response 
{
  "cve_id": "CVE-2016-8562",
  "confidence": "Confirmed",
  "cvss_score": 7.5,
  "cvss_estimated": false,
  "epss_score": 0.0361,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}