Skip to content
Noroxi
CVE-2016-9159· NVD / CVE Program· CNA siemens

A vulnerability has been identified in SIMATIC S7-300 CPU family (All versions), SIMATIC S7-300 CPU family (incl.

A vulnerability has been identified in SIMATIC S7-300 CPU family (All versions), SIMATIC S7-300 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions), SIMATIC S7-400 PN/DP V6 and below CPU family (incl. SIPLUS variants) (All versions), SIMATIC S7-400 PN/DP V7 CPU family (incl. SIPLUS variants) (All versions), SIMATIC S7-400 V6 and earlier CPU family (All versions), SIMATIC S7-400 V7 CPU family (All versions), SIMATIC S7-410 V8 CPU family (All versions), SIMATIC S7-410 V8 CPU family (incl. SIPLUS variants) (All versions). An attacker with network access to port 102/tcp (ISO-TSAP) or via Profibus could obtain credentials from the PLC if protection-level 2 is configured on the affected devices.

MediumCVSS 5.9 · v3.1—No exploit No fix recorded
Published
Dec 16, 2016
Updated
Jun 16, 2026
EPSS
1.5% · 74th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
siemenssimatic s7-300 cpu firmware
siemenssimatic s7-300 cpu 312
siemenssimatic s7-300 cpu 314
siemenssimatic s7-300 cpu 315-2 dp
siemenssimatic s7-300 cpu 315-2 pn\/dp
siemenssimatic s7-300 cpu 317- 2 dp
siemenssimatic s7-300 cpu 317-2 pn\/dp
siemenssimatic s7-300 cpu 319-3 pn\/dp
siemenssimatic s7-400 cpu firmware
siemenssimatic s7-400 cpu 412-1
siemenssimatic s7-400 cpu 412-2
siemenssimatic s7-400 cpu 412-2 pn

and 9 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • siemens simatic s7-300 cpu firmwareall versions
  • siemens simatic s7-400 cpu firmwareall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (siemens). Independent of NVD's CPE analysis and usually ahead of it.

  • Siemens AG SIMATIC S7-300 CPU family

    • All versionsaffected

  • Siemens AG SIMATIC S7-300 CPU family (incl. related ET200 CPUs and SIPLUS variants)

    • All versionsaffected

  • Siemens AG SIMATIC S7-400 PN/DP V6 and below CPU family (incl. SIPLUS variants)

    • All versionsaffected

  • Siemens AG SIMATIC S7-400 PN/DP V7 CPU family (incl. SIPLUS variants)

    • All versionsaffected

  • Siemens AG SIMATIC S7-400 V6 and earlier CPU family

    • All versionsaffected

  • Siemens AG SIMATIC S7-400 V7 CPU family

    • All versionsaffected

  • Siemens AG SIMATIC S7-410 V8 CPU family

    • All versionsaffected

  • Siemens AG SIMATIC S7-410 V8 CPU family (incl. SIPLUS variants)

    • All versionsaffected

Same product

siemens: all records

Other highest-scoring records for the same primary product.

  • CVE-2015-2177Siemens SIMATIC S7-300 CPU devices allow remote attackers to cause a denial of service (defect-mode transition) via crafted packets on (1) T
    40Plan
  • CVE-2019-18336A vulnerability has been identified in SIMATIC S7-300 CPU family (incl.
    31Monitor
  • CVE-2016-9158A vulnerability has been identified in SIMATIC S7-300 CPU family (All versions), SIMATIC S7-300 CPU family (incl.
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

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

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records