# CVE-2022-36324: Denial of service in RUGGEDCOM RM1224 LTE(4G) EU

> An unauthenticated remote attacker can cause a denial of service by exploiting improper SSL/TLS renegotiation handling in Siemens industrial routers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2022
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-hm3h-qvm3-r8qv

## What is CVE-2022-36324?

CVE-2022-36324 is a high-severity denial of service vulnerability in Siemens RUGGEDCOM RM1224 LTE(4G) EU, published on 10 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected devices do not properly handle the renegotiation of SSL/TLS parameters. This could allow an unauthenticated remote attacker to bypass the TCP brute force prevention and lead to a denial of service condition for the duration of the attack.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 84 products.


Products: Siemens Scalance M-800 Firmware, Siemens Scalance S615 Firmware, Siemens Scalance W700 Ieee 802.11ac Firmware, Siemens Scalance W700 Ieee 802.11ax Firmware, Siemens Scalance W700 Ieee 802.11n Firmware, Siemens Scalance Xb-200 Firmware, Siemens Scalance Xb205-3 Firmware, Siemens Scalance Xb205-3ld Firmware, Siemens Scalance Xb208 Firmware, Siemens Scalance Xb213-3 Firmware, Siemens Scalance Xb213-3ld Firmware, Siemens Scalance Xb216 Firmware, Siemens Scalance Xc-200 Firmware, Siemens Scalance Xc206-2 Firmware, Siemens Scalance Xc206-2g Poe  Firmware, Siemens Scalance Xc206-2g Poe Eec Firmware, Siemens Scalance Xc206-2sfp Eec Firmware, Siemens Scalance Xc206-2sfp G \(E\/Ip\) Firmware, Siemens Scalance Xc206-2sfp G Eec Firmware, Siemens Scalance Xc206-2sfp G Firmware and 64 more.

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

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

## Is CVE-2022-36324 being exploited?

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

## Other vulnerabilities in Siemens RUGGEDCOM RM1224 LTE(4G) EU

- [CVE-2022-36323](https://insights.sbomify.com/CVE-2022-36323/): Command injection in RUGGEDCOM RM1224 LTE(4G) EU (critical 9.1)
- [CVE-2022-36325](https://insights.sbomify.com/CVE-2022-36325/): Cross-site scripting in RUGGEDCOM RM1224 LTE(4G) EU (medium 6.8)
- [CVE-2016-7090](https://insights.sbomify.com/CVE-2016-7090/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36324 is a high-severity denial of service vulnerability in Siemens RUGGEDCOM RM1224 LTE(4G) EU, published on 10 Aug 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-36324 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM RM1224 LTE(4G) EU. 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-36324/ (Markdown: https://insights.sbomify.com/CVE-2022-36324/index.md)
```

## Sources

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

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