# CVE-2024-56181: Security feature bypass in SIMATIC Field PG M5

> An authenticated attacker can bypass Secure Boot by modifying EFI variables via direct flash controller communication on Siemens SIMATIC devices.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-wpmj-mx2h-xgfx

## What is CVE-2024-56181?

CVE-2024-56181 is a high-severity vulnerability in Siemens SIMATIC Field PG M5, published on 11 Mar 2025. 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 Field PG M5 (All versions), SIMATIC IPC BX-21A (All versions < V31.01.07), SIMATIC IPC BX-32A (All versions < V29.01.07), SIMATIC IPC BX-39A (All versions < V29.01.07), SIMATIC IPC BX-59A (All versions < V32.01.04), SIMATIC IPC PX-32A (All versions < V29.01.07), SIMATIC IPC PX-39A (All versions < V29.01.07), SIMATIC IPC PX-39A PRO (All versions < V29.01.07), SIMATIC IPC RC-543A (All versions < V36.01.03), SIMATIC IPC RC-543B (All versions < V35.01.12), SIMATIC IPC RW-543A (All versions < V1.1.4), SIMATIC IPC RW-543B (All versions < V35.02.10), SIMATIC IPC127E (All versions < V27.01.11), SIMATIC IPC227E (All versions), SIMATIC IPC227G (All versions < V28.01.14), SIMATIC IPC277E (All versions), SIMATIC IPC277G (All versions < V28.01.14), SIMATIC IPC277G PRO (All versions < V28.01.14), SIMATIC IPC3000 SMART V3 (All versions), SIMATIC IPC327G (All versions < V28.01.14), SIMATIC IPC347G (All versions), SIMATIC IPC377G (All versions < V28.01.14), SIMATIC IPC427E (All versions < V21.01.21), SIMATIC IPC477E (All versions < V21.01.21), SIMATIC IPC477E PRO (All versions < V21.01.21), SIMATIC IPC527G (All versions), SIMATIC IPC627E (All versions < V25.02.15), SIMATIC IPC647E (All versions < V25.02.15), SIMATIC IPC677E (All versions < V25.02.15), SIMATIC IPC847E (All versions < V25.02.15), SIMATIC ITP1000 (All versions). The affected devices have insufficient protection mechanism for the EFI(Extensible Firmware Interface) variables stored on the device. This could allow an authenticated attacker to alter the secure boot configuration without proper authorization by directly communicate with the flash controller.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2024-56181?


## How do I fix CVE-2024-56181?

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

## Is CVE-2024-56181 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56181 and fix it if it is affected.

What it is: CVE-2024-56181 is a high-severity vulnerability in Siemens SIMATIC Field PG M5, published on 11 Mar 2025. 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-2024-56181 in the wild and no public exploit code.

Affected product: Siemens SIMATIC Field PG M5. 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-2024-56181/ (Markdown: https://insights.sbomify.com/CVE-2024-56181/index.md)
```

## Sources

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

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