# CVE-2021-25667: Memory corruption in RUGGEDCOM RM1224

> Remote attackers can cause denial of service or execute code via stack-based buffer overflow in STP BPDU handling on Siemens SCALANCE devices with passive listening enabled.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2021
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-p672-97f8-chmq

## What is CVE-2021-25667?

CVE-2021-25667 is a medium-severity memory corruption vulnerability in Siemens RUGGEDCOM RM1224, published on 15 Mar 2021. 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 RUGGEDCOM RM1224 (All versions >= V4.3 and < V6.4), SCALANCE M-800 (All versions >= V4.3 and < V6.4), SCALANCE S615 (All versions >= V4.3 and < V6.4), SCALANCE SC-600 Family (All versions >= V2.0 and < V2.1.3), SCALANCE XB-200 (All versions < V4.1), SCALANCE XC-200 (All versions < V4.1), SCALANCE XF-200BA (All versions < V4.1), SCALANCE XM400 (All versions < V6.2), SCALANCE XP-200 (All versions < V4.1), SCALANCE XR-300WG (All versions < V4.1), SCALANCE XR500 (All versions < V6.2). Affected devices contain a stack-based buffer overflow vulnerability in the handling of STP BPDU frames that could allow a remote attacker to trigger a denial-of-service condition or potentially remote code execution. Successful exploitation requires the passive listening feature of the device to be active.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2021-25667?

It affects 15 products.


Products: Siemens Ruggedcom Rm1224 Firmware, Siemens Scalance M-800 Firmware, Siemens Scalance S615 Firmware, Siemens Scalance Sc622-2c Firmware, Siemens Scalance Sc632-2c Firmware, Siemens Scalance Sc636-2c Firmware, Siemens Scalance Sc642-2c Firmware, Siemens Scalance Sc646-2c Firmware, Siemens Scalance X300wg Firmware, Siemens Scalance Xb-200 Firmware, Siemens Scalance Xc-200 Firmware, Siemens Scalance Xf-200ba Firmware, Siemens Scalance Xm400 Firmware, Siemens Scalance Xp-200 Firmware, Siemens Scalance Xr500 Firmware.

## How do I fix CVE-2021-25667?

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

## Is CVE-2021-25667 being exploited?

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

## Other vulnerabilities in Siemens RUGGEDCOM RM1224

- [CVE-2022-31766](https://insights.sbomify.com/CVE-2022-31766/): Other in RUGGEDCOM RM1224 LTE(4G) EU (high 8.6)
- [CVE-2021-25676](https://insights.sbomify.com/CVE-2021-25676/): Denial of service in RUGGEDCOM RM1224 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25667 and fix it if it is affected.

What it is: CVE-2021-25667 is a medium-severity memory corruption vulnerability in Siemens RUGGEDCOM RM1224, published on 15 Mar 2021. 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-2021-25667 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM RM1224. 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-2021-25667/ (Markdown: https://insights.sbomify.com/CVE-2021-25667/index.md)
```

## Sources

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

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