CVE-2019-13940: A vulnerability has been identified in SIMATIC ET 200pro IM154-8 PN/DP CPU (All versions < V3.X.17), SIMATIC ET 200pro IM154-8F PN/DP CPU…
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.6% 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 the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 7.5.
- Mentioned 3 times 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 ET 200pro IM154-8 PN/DP CPU (All versions < V3.X.17), SIMATIC ET 200pro IM154-8F PN/DP CPU (All versions < V3.X.17), SIMATIC ET 200pro IM154-8FX PN/DP CPU (All versions < V3.X.17), SIMATIC ET 200S IM151-8 PN/DP CPU (All versions < V3.X.17), SIMATIC ET 200S IM151-8F PN/DP CPU (All versions < V3.X.17), SIMATIC S7-1200 CPU family (incl. SIPLUS variants) (All versions < V4.1), SIMATIC S7-300 CPU 314C-2 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 315-2 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 315F-2 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 315T-3 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 317-2 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 317F-2 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 317T-3 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 317TF-3 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 319-3 PN/DP (All versions < V3.X.17), SIMATIC S7-300 CPU 319F-3 PN/DP (All versions < V3.X.17), 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 WinAC RTX 2010 (All versions), SIMATIC WinAC RTX F 2010 (All versions), SIPLUS ET 200S IM151-8 PN/DP CPU (All versions < V3.X.17), SIPLUS ET 200S IM151-8F PN/DP CPU (All versions < V3.X.17), SIPLUS S7-300 CPU 314C-2 PN/DP (All versions < V3.X.17), SIPLUS S7-300 CPU 315-2 PN/DP (All versions < V3.X.17), SIPLUS S7-300 CPU 315F-2 PN/DP (All versions < V3.X.17), SIPLUS S7-300 CPU 317-2 PN/DP (All versions < V3.X.17), SIPLUS S7-300 CPU 317F-2 PN/DP (All versions < V3.X.17). Affected devices contain a vulnerability that could cause a denial of service condition of the web server by sending specially crafted HTTP requests to ports 80/tcp and 443/tcp. Beyond the web service, no other functions or interfaces are affected by the denial of service condition.
- Published
- Feb 11, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.7% · 77th percentile
- CWE
- CWE-400
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
CNA vs NVD score
- NVD
- 7.5
- CNA · siemens
- 5.3
- 2.2 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 | s7-1200 cpu 1211c firmware | cpe:2.3:o:siemens:s7-1200_cpu_1211c_firmware |
| siemens | s7-1200 cpu 1211c | cpe:2.3:h:siemens:s7-1200_cpu_1211c |
| siemens | s7-1200 cpu 1212c firmware | cpe:2.3:o:siemens:s7-1200_cpu_1212c_firmware |
| siemens | s7-1200 cpu 1212c | cpe:2.3:h:siemens:s7-1200_cpu_1212c |
| siemens | s7-1200 cpu 1214c firmware | cpe:2.3:o:siemens:s7-1200_cpu_1214c_firmware |
| siemens | s7-1200 cpu 1214c | cpe:2.3:h:siemens:s7-1200_cpu_1214c |
| siemens | s7-1200 cpu 1215c firmware | cpe:2.3:o:siemens:s7-1200_cpu_1215c_firmware |
| siemens | s7-1200 cpu 1215c | cpe:2.3:h:siemens:s7-1200_cpu_1215c |
| siemens | s7-1200 cpu 1217c firmware | cpe:2.3:o:siemens:s7-1200_cpu_1217c_firmware |
| siemens | s7-1200 cpu 1217c | cpe:2.3:h:siemens:s7-1200_cpu_1217c |
| siemens | s7-1200 cpu 1212fc firmware | cpe:2.3:o:siemens:s7-1200_cpu_1212fc_firmware |
| siemens | s7-1200 cpu 1212fc | cpe:2.3:h:siemens:s7-1200_cpu_1212fc |
and 35 more
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 SIMATIC ET 200pro IM154-8 PN/DP CPU
- All versions < V3.X.17affected
Siemens SIMATIC ET 200pro IM154-8F PN/DP CPU
- All versions < V3.X.17affected
Siemens SIMATIC ET 200pro IM154-8FX PN/DP CPU
- All versions < V3.X.17affected
Siemens SIMATIC ET 200S IM151-8 PN/DP CPU
- All versions < V3.X.17affected
Siemens SIMATIC ET 200S IM151-8F PN/DP CPU
- All versions < V3.X.17affected
Siemens SIMATIC S7-1200 CPU family (incl. SIPLUS variants)
- All versions < V4.1affected
Siemens SIMATIC S7-300 CPU 314C-2 PN/DP
- All versions < V3.X.17affected
Siemens SIMATIC S7-300 CPU 315-2 PN/DP
- All versions < V3.X.17affected
Siemens SIMATIC S7-300 CPU 315F-2 PN/DP
- All versions < V3.X.17affected
Siemens SIMATIC S7-300 CPU 315T-3 PN/DP
- All versions < V3.X.17affected
Siemens SIMATIC S7-300 CPU 317-2 PN/DP
- All versions < V3.X.17affected
Siemens SIMATIC S7-300 CPU 317F-2 PN/DP
- All versions < V3.X.17affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- siemens s7-1200 cpu 1211c firmwarebefore 4.1
- siemens s7-1200 cpu 1212c firmwarebefore 4.1
- siemens s7-1200 cpu 1212fc firmwarebefore 4.1
- siemens s7-1200 cpu 1214c firmwarebefore 4.1
- siemens s7-1200 cpu 1214fc firmwarebefore 4.1
- siemens s7-1200 cpu 1215c firmwarebefore 4.1
- siemens s7-1200 cpu 1215fc firmwarebefore 4.1
- siemens s7-1200 cpu 1217c firmwarebefore 4.1
- siemens simatic s7-300 cpu 315-2 pn/dp firmwareall versions
- siemens simatic s7-300 cpu 315-2dp firmwareall versions
- siemens simatic s7-300 cpu 317-2 dp firmwareall versions
- siemens simatic s7-300 cpu 317-2 pn/dp firmwareall versions
- siemens simatic s7-300 cpu 319-3 pn/dp firmwareall versions
- siemens simatic s7-400 pn/dp cpu firmwareall versions
- siemens simatic winac rtx (f) 2010all versions
- siemens siplus cpu 1211c firmwarebefore 4.1
- siemens siplus cpu 1212c firmwarebefore 4.1
- siemens siplus cpu 1214c firmwareup to 4.1 inclusive
- siemens siplus cpu 1215c firmwarebefore 4.1
- siemens siplus s7-1200 firmwarebefore 4.1
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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-226 · Apr 15, 2020(Siemens Endüstriyel Ürünler Zafiyeti)
- TR-20-132 · Mar 10, 2020(Siemens Endüstriyel Ürünler Zafiyeti)
- TR-20-080 · Feb 11, 2020(Siemens Endüstriyel Ürünler Zafiyeti)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (0)
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.