# CVE-2022-36363: Information disclosure in LOGO! 12/24RCE

> An attacker can retrieve parts of memory content by sending crafted TCP packets to affected Siemens LOGO! devices due to improper offset validation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:T/RC:C`)
- **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:** 8 Oct 2024
- **Also known as:** GHSA-j45q-g2vj-3f3r

## What is CVE-2022-36363?

CVE-2022-36363 is a medium-severity vulnerability in Siemens LOGO! 12/24RCE, 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 LOGO! 12/24RCE (6ED1052-1MD08-0BA1) (All versions), LOGO! 12/24RCEo (6ED1052-2MD08-0BA1) (All versions), LOGO! 230RCE (6ED1052-1FB08-0BA1) (All versions), LOGO! 230RCEo (6ED1052-2FB08-0BA1) (All versions), LOGO! 24CE (6ED1052-1CC08-0BA1) (All versions), LOGO! 24CEo (6ED1052-2CC08-0BA1) (All versions), LOGO! 24RCE (6ED1052-1HB08-0BA1) (All versions), LOGO! 24RCEo (6ED1052-2HB08-0BA1) (All versions), SIPLUS LOGO! 12/24RCE (6AG1052-1MD08-7BA1) (All versions), SIPLUS LOGO! 12/24RCEo (6AG1052-2MD08-7BA1) (All versions), SIPLUS LOGO! 230RCE (6AG1052-1FB08-7BA1) (All versions), SIPLUS LOGO! 230RCEo (6AG1052-2FB08-7BA1) (All versions), SIPLUS LOGO! 24CE (6AG1052-1CC08-7BA1) (All versions), SIPLUS LOGO! 24CEo (6AG1052-2CC08-7BA1) (All versions), SIPLUS LOGO! 24RCE (6AG1052-1HB08-7BA1) (All versions), SIPLUS LOGO! 24RCEo (6AG1052-2HB08-7BA1) (All versions). Affected devices do not properly validate an offset value which can be defined in TCP packets when calling a method. This could allow an attacker to retrieve parts of the content of the memory.

Weakness: CWE-20 (Improper Input Validation), CWE-1285 (Improper Validation of Specified Index, Position, or Offset in Input)

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

It affects 2 products.


Products: Siemens Logo\!8 Bm Fs-05 Firmware, Siemens Logo\! 8 Bm Firmware.

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

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

## Is CVE-2022-36363 being exploited?

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

## Other vulnerabilities in Siemens LOGO! 12/24RCE

- [CVE-2022-36361](https://insights.sbomify.com/CVE-2022-36361/): Memory corruption in LOGO! 12/24RCE (critical 9.8)
- [CVE-2022-36360](https://insights.sbomify.com/CVE-2022-36360/): Security feature bypass in LOGO! 8 BM (incl. SIPLUS variants) (high 7.5)
- [CVE-2022-36362](https://insights.sbomify.com/CVE-2022-36362/): Missing authorization in LOGO! 12/24RCE (high 7.5)
- [CVE-2017-12734](https://insights.sbomify.com/CVE-2017-12734/): Information disclosure in LOGO! 8 BM (incl. SIPLUS variants) (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36363 is a medium-severity vulnerability in Siemens LOGO! 12/24RCE, 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-36363 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-36363/ (Markdown: https://insights.sbomify.com/CVE-2022-36363/index.md)
```

## Sources

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

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