# CVE-2022-40227: Denial of service in SIMATIC HMI Comfort Panels (incl. SIPLUS variants)

> Unauthenticated remote attackers can cause permanent denial of service on Siemens HMI panels by sending crafted TCP packets, requiring device reboot.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2022
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-3w5w-5g86-h65c

## What is CVE-2022-40227?

CVE-2022-40227 is a high-severity denial of service vulnerability in Siemens SIMATIC HMI Comfort Panels (incl. SIPLUS variants), published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in SIMATIC HMI Comfort Panels (incl. SIPLUS variants) (All versions < V17 Update 4), SIMATIC HMI KTP Mobile Panels (All versions < V17 Update 4), SIMATIC HMI KTP1200 Basic (All versions < V17 Update 5), SIMATIC HMI KTP400 Basic (All versions < V17 Update 5), SIMATIC HMI KTP700 Basic (All versions < V17 Update 5), SIMATIC HMI KTP900 Basic (All versions < V17 Update 5), SIPLUS HMI KTP1200 BASIC (All versions < V17 Update 5), SIPLUS HMI KTP400 BASIC (All versions < V17 Update 5), SIPLUS HMI KTP700 BASIC (All versions < V17 Update 5), SIPLUS HMI KTP900 BASIC (All versions < V17 Update 5). Affected devices do not properly validate input sent to certain services over TCP. This could allow an unauthenticated remote attacker to cause a permanent denial of service condition (requiring a device reboot) by sending specially crafted TCP packets.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-40227?

It affects 10 products.


Products: Siemens Simatic Hmi Comfort Panels Firmware, Siemens Simatic Hmi Ktp1200 Basic Firmware, Siemens Simatic Hmi Ktp400 Basic Firmware, Siemens Simatic Hmi Ktp700 Basic Firmware, Siemens Simatic Hmi Ktp900 Basic Firmware, Siemens Simatic Hmi Ktp Mobile Panels Firmware, Siemens Siplus Hmi Ktp1200 Basic Firmware, Siemens Siplus Hmi Ktp400 Basic Firmware, Siemens Siplus Hmi Ktp700 Basic Firmware, Siemens Siplus Hmi Ktp900 Basic Firmware.

## How do I fix CVE-2022-40227?

No fix has been published for CVE-2022-40227 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-40227 being exploited?

There is no known exploitation of CVE-2022-40227 in the wild and no public exploit code.

## Other vulnerabilities in Siemens SIMATIC HMI Comfort Panels (incl. SIPLUS variants)

- [CVE-2020-15798](https://insights.sbomify.com/CVE-2020-15798/): Auth bypass in SIMATIC HMI Comfort Panels (incl. SIPLUS variants) (critical 9.8)
- [CVE-2019-19276](https://insights.sbomify.com/CVE-2019-19276/): Denial of service in SIMATIC HMI Comfort Panels 1st Generation (incl. SIPLUS variants) (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40227 and fix it if it is affected.

What it is: CVE-2022-40227 is a high-severity denial of service vulnerability in Siemens SIMATIC HMI Comfort Panels (incl. SIPLUS variants), published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40227 in the wild and no public exploit code.

Affected product: Siemens SIMATIC HMI Comfort Panels (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-2022-40227/ (Markdown: https://insights.sbomify.com/CVE-2022-40227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-40227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-40227
- OSV: https://osv.dev/vulnerability/CVE-2022-40227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-40227/
Summaries are generated and may contain mistakes; the official description above is the record.