# CVE-2018-4843: Other in SIMATIC CP 343-1 (incl. SIPLUS variants) > Attackers can cause a denial of service on Siemens SIMATIC PLCs and communication processors via improper input validation. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 20 Mar 2018 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-2cg6-w8mm-22rg ## What is CVE-2018-4843? CVE-2018-4843 is a medium-severity vulnerability in Siemens SIMATIC CP 343-1 (incl. SIPLUS variants), published on 20 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A vulnerability has been identified in SIMATIC S7-400 CPU 414-3 PN/DP V7 (All versions < V7.0.3), SIMATIC S7-400 CPU 414F-3 PN/DP V7 (All versions < V7.0.3), SIMATIC S7-400 CPU 416-3 PN/DP V7 (All versions < V7.0.3), SIMATIC S7-400 CPU 416F-3 PN/DP V7 (All versions < V7.0.3), SIMATIC CP 343-1 (incl. SIPLUS variants) (All versions), SIMATIC CP 343-1 Advanced (incl. SIPLUS variants) (All versions), SIMATIC CP 443-1 (All versions < V3.3), SIMATIC CP 443-1 (All versions < V3.3), SIMATIC CP 443-1 Advanced (All versions < V3.3), SIMATIC ET 200pro IM154-8 PN/DP CPU (All versions < V3.2.16), SIMATIC ET 200pro IM154-8F PN/DP CPU (All versions < V3.2.16), SIMATIC ET 200pro IM154-8FX PN/DP CPU (All versions < V3.2.16), SIMATIC ET 200S IM151-8 PN/DP CPU (All versions < V3.2.16), SIMATIC ET 200S IM151-8F PN/DP CPU (All versions < V3.2.16), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions < V1.7.0), SIMATIC S7-1500 Software Controller (All versions < V1.7.0), SIMATIC S7-300 CPU 314C-2 PN/DP (All versions < V3.3.16), SIMATIC S7-300 CPU 315-2 PN/DP (All versions < V3.2.16), SIMATIC S7-300 CPU 315F-2 PN/DP (All versions < V3.2.16), SIMATIC S7-300 CPU 315T-3 PN/DP (All versions < V3.2.16), SIMATIC S7-300 CPU 317-2 PN/DP (All versions < V3.2.16), SIMATIC S7-300 CPU 317F-2 PN/DP (All versions < V3.2.16), SIMATIC S7-300 CPU 317T-3 PN/DP (All versions < V3.2.16), SIMATIC S7-300 CPU 317TF-3 PN/DP (All versions < V3.2.16), SIMATIC S7-300 CPU 319-3 PN/DP (All versions < V3.2.16), SIMATIC S7-300 CPU 319F-3 PN/DP (All versions < V3.2.16), SIMATIC S7-400 CPU 412-2 PN V7 (All versions < V7.0.3), SIMATIC S7-400 H V6 CPU family (incl. SIPLUS variants) (All versions < V6.0.9), SIMATIC S7-400 PN/DP V6 CPU family (incl. SIPLUS variants) (All versions < V6.0.7), SIMATIC S7-410 CPU family (incl. SIPLUS variants) (All versions < V8.1), SIMATIC WinAC RTX 2010 (All versions < V2010 SP3), SIMATIC WinAC RTX F 2010 (All versions < V2010 SP3), SINUMERIK 828D (All versions < V4.7 SP6 HF1), SIPLUS ET 200S IM151-8 PN/DP CPU (All versions < V3.2.16), SIPLUS ET 200S IM151-8F PN/DP CPU (All versions < V3.2.16), SIPLUS NET CP 443-1 (All versions < V3.3), SIPLUS NET CP 443-1 Advanced (All versions < V3.3), SIPLUS S7-300 CPU 314C-2 PN/DP (All versions < V3.3.16), SIPLUS S7-300 CPU 315-2 PN/DP (All versions < V3.2.16), SIPLUS S7-300 CPU 315F-2 PN/DP (All versions < V3.2.16), SIPLUS S7-300 CPU 317-2 PN/DP (All versions < V3.2.16), SIPLUS S7-300 CPU 317F-2 PN/DP (All versions < V3.2.16), SIPLUS S7-400 CPU 414-3 PN/DP V7 (All versions < V7.0.3), SIPLUS S7-400 CPU 416-3 PN/DP V7 (All versions < V7.0.3), Softnet PROFINET IO for PC-based Windows systems (All versions). Responding to a PROFINET DCP request with a specially crafted PROFINET DCP packet could cause a denial of service condition of the requesting system. The security vulnerability could be exploited by an attacker located on the same Ethernet segment (OSI Layer 2) as the targeted device. A manual restart is required to recover the system. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2018-4843? It affects 11 products. Products: Siemens Simatic Cp 343-1 Firmware, Siemens Simatic Cp 443-1 Firmware, Siemens Simatic S7-1500 Firmware, Siemens Simatic S7-300 Firmware, Siemens Simatic S7-400 H V6 Firmware, Siemens Simatic S7-400 Pn\/Dp V6 Firmware, Siemens Simatic S7-400 Pn\/Dp V7 Firmware, Siemens Simatic S7-410 Firmware, Siemens Simatic Winac Rtx 2010 Firmware, Siemens Sinumerik 828d Firmware, Siemens Softnet Pn-Io Linux Firmware. ## How do I fix CVE-2018-4843? No fix has been published for CVE-2018-4843 yet. Limit exposure of the affected software until one is available. ## Is CVE-2018-4843 being exploited? There is no known exploitation of CVE-2018-4843 in the wild and no public exploit code. ## Other vulnerabilities in Siemens SIMATIC CP 343-1 (incl. SIPLUS variants) - [CVE-2015-8214](https://insights.sbomify.com/CVE-2015-8214/): Missing authorization in n/a (critical 9.7) - [CVE-2016-8673](https://insights.sbomify.com/CVE-2016-8673/): Cross-site request forgery in n/a (high 8.8) - [CVE-2023-51440](https://insights.sbomify.com/CVE-2023-51440/): Denial of service in SIMATIC CP 343-1 (high 7.5) - [CVE-2016-8672](https://insights.sbomify.com/CVE-2016-8672/): Information disclosure in n/a (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-4843 and fix it if it is affected. What it is: CVE-2018-4843 is a medium-severity vulnerability in Siemens SIMATIC CP 343-1 (incl. SIPLUS variants), published on 20 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2018-4843 in the wild and no public exploit code. Affected product: Siemens SIMATIC CP 343-1 (incl. SIPLUS variants). No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-4843/ (Markdown: https://insights.sbomify.com/CVE-2018-4843/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-4843 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-4843 - OSV: https://osv.dev/vulnerability/CVE-2018-4843 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-4843/ Summaries are generated and may contain mistakes; the official description above is the record.