# CVE-2022-42784: Security feature bypass in LOGO! 12/24RCE

> Physical electromagnetic fault injection allows attackers to dump firmware and inject custom keys, enabling device impersonation and communication interception.

- **Severity:** High 7.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/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:** 12 Dec 2023
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-g38w-3g42-rgpg

## What is CVE-2022-42784?

CVE-2022-42784 is a high-severity vulnerability in Siemens LOGO! 12/24RCE, published on 12 Dec 2023. 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 LOGO! 12/24RCE (6ED1052-1MD08-0BA1) (All versions >= V8.3), LOGO! 12/24RCEo (6ED1052-2MD08-0BA1) (All versions >= V8.3), LOGO! 230RCE (6ED1052-1FB08-0BA1) (All versions >= V8.3), LOGO! 230RCEo (6ED1052-2FB08-0BA1) (All versions >= V8.3), LOGO! 24CE (6ED1052-1CC08-0BA1) (All versions >= V8.3), LOGO! 24CEo (6ED1052-2CC08-0BA1) (All versions >= V8.3), LOGO! 24RCE (6ED1052-1HB08-0BA1) (All versions >= V8.3), LOGO! 24RCEo (6ED1052-2HB08-0BA1) (All versions >= V8.3), SIPLUS LOGO! 12/24RCE (6AG1052-1MD08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 12/24RCEo (6AG1052-2MD08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 230RCE (6AG1052-1FB08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 230RCEo (6AG1052-2FB08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 24CE (6AG1052-1CC08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 24CEo (6AG1052-2CC08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 24RCE (6AG1052-1HB08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 24RCEo (6AG1052-2HB08-7BA1) (All versions >= V8.3). Affected devices are vulnerable to an electromagnetic fault injection. This could allow an attacker to dump and debug the firmware, including the manipulation of memory. Further actions could allow to inject public keys of custom created key pairs which are then signed by the product CA. The generation of a custom certificate allows communication with, and impersonation of, any device of the same version.

Weakness: CWE-1319 (Improper Protection against Electromagnetic Fault Injection (EM-FI))

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

It affects 16 products.


Products: Siemens 6ag1052-1cc08-7ba1 Firmware, Siemens 6ag1052-1fb08-7ba1 Firmware, Siemens 6ag1052-1hb08-7ba1 Firmware, Siemens 6ag1052-1md08-7ba1 Firmware, Siemens 6ag1052-2cc08-7ba1 Firmware, Siemens 6ag1052-2fb08-7ba1 Firmware, Siemens 6ag1052-2hb08-7ba1 Firmware, Siemens 6ag1052-2md08-7ba1 Firmware, Siemens 6ed1052-1cc08-0ba1 Firmware, Siemens 6ed1052-1fb08-0ba1 Firmware, Siemens 6ed1052-1hb08-0ba1 Firmware, Siemens 6ed1052-1md08-0ba1 Firmware, Siemens 6ed1052-2cc08-0ba1 Firmware, Siemens 6ed1052-2fb08-0ba1 Firmware, Siemens 6ed1052-2hb08-0ba1 Firmware, Siemens 6ed1052-2md08-0ba1 Firmware.

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

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

## Is CVE-2022-42784 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42784 is a high-severity vulnerability in Siemens LOGO! 12/24RCE, published on 12 Dec 2023. 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-2022-42784 in the wild and no public exploit code.

Affected product: Siemens LOGO! 12/24RCE. 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-42784/ (Markdown: https://insights.sbomify.com/CVE-2022-42784/index.md)
```

## Sources

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

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