A vulnerability has been identified in SIMATIC S7-300 CPU family (incl.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 77% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability has been identified in SIMATIC S7-300 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions < V3.X.17), SIMATIC TDC CP51M1 (All versions < V1.1.8), SIMATIC TDC CPU555 (All versions < V1.1.1), SINUMERIK 840D sl (All versions < V4.8.6), SINUMERIK 840D sl (All versions < V4.94). Specially crafted packets sent to port 102/tcp (Profinet) could cause the affected device to go into defect mode. A restart is required in order to recover the system. Successful exploitation requires an attacker to have network access to port 102/tcp, with no authentication. No user interation is required. At the time of advisory publication no public exploitation of this security vulnerability was known.
- Published
- Mar 10, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.7% · 77th percentile
- CWE
- CWE-400
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| siemens | simatic s7-300 cpu firmware | cpe:2.3:o:siemens:simatic_s7-300_cpu_firmware |
| siemens | simatic s7-300 cpu | cpe:2.3:h:siemens:simatic_s7-300_cpu |
| siemens | simatic s7-300 cpu 312 ifm firmware | cpe:2.3:o:siemens:simatic_s7-300_cpu_312_ifm_firmware |
| siemens | simatic s7-300 cpu 312 ifm | cpe:2.3:h:siemens:simatic_s7-300_cpu_312_ifm |
| siemens | simatic s7-300 cpu 313 firmware | cpe:2.3:o:siemens:simatic_s7-300_cpu_313_firmware |
| siemens | simatic s7-300 cpu 313 | cpe:2.3:h:siemens:simatic_s7-300_cpu_313 |
| siemens | simatic s7-300 cpu 314 firmware | cpe:2.3:o:siemens:simatic_s7-300_cpu_314_firmware |
| siemens | simatic s7-300 cpu 314 | cpe:2.3:h:siemens:simatic_s7-300_cpu_314 |
| siemens | simatic s7-300 cpu 314 ifm firmware | cpe:2.3:o:siemens:simatic_s7-300_cpu_314_ifm_firmware |
| siemens | simatic s7-300 cpu 314 ifm | cpe:2.3:h:siemens:simatic_s7-300_cpu_314_ifm |
| siemens | simatic s7-300 cpu 315 firmware | cpe:2.3:o:siemens:simatic_s7-300_cpu_315_firmware |
| siemens | simatic s7-300 cpu 315 | cpe:2.3:h:siemens:simatic_s7-300_cpu_315 |
and 11 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 312 ifm firmwarebefore 3.3.17
- siemens simatic s7-300 cpu 313 firmwarebefore 3.3.17
- siemens simatic s7-300 cpu 314 firmwarebefore 3.3.17
- siemens simatic s7-300 cpu 314 ifm firmwarebefore 3.3.17
- siemens simatic s7-300 cpu 315 firmwarebefore 3.3.17
- siemens simatic s7-300 cpu 315-2 dp firmwarebefore 3.3.17
- siemens simatic s7-300 cpu 316-2 dp firmwarebefore 3.3.17
- siemens simatic s7-300 cpu 318-2 firmwarebefore 3.3.17
- siemens simatic s7-300 cpu firmwarebefore 3.3.17
- siemens simatic tdc cp51m1 firmwarebefore 1.1.8
- siemens simatic tdc cpu555 firmwarebefore 1.1.1
- siemens sinumerik 840d slbefore 4.8.6
- siemens sinumerik 840d slbefore 4.94
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 (incl. related ET200 CPUs and SIPLUS variants)
- All versions < V3.X.17affected
Siemens AG SIMATIC TDC CP51M1
- All versions < V1.1.8affected
Siemens AG SIMATIC TDC CPU555
- All versions < V1.1.1affected
Siemens AG SINUMERIK 840D sl
- All versions < V4.8.6, All versions < V4.94affected
Same product
siemens: all recordsOther 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) T40Plan
- CVE-2016-9158A vulnerability has been identified in SIMATIC S7-300 CPU family (All versions), SIMATIC S7-300 CPU family (incl.31Monitor
- CVE-2016-9159A vulnerability has been identified in SIMATIC S7-300 CPU family (All versions), SIMATIC S7-300 CPU family (incl.23Monitor
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.
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-132 · Mar 10, 2020(Siemens Endüstriyel Ürünler Zafiyeti)
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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.