# CVE-2021-31895: Memory corruption in RUGGEDCOM M2100 > A memory corruption vulnerability in Siemens RUGGEDCOM devices allows attackers to execute arbitrary code or cause a denial of service. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/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:** 13 Jul 2021 - **Updated:** 14 Oct 2025 - **Also known as:** GHSA-29cc-vcq3-44cf ## What is CVE-2021-31895? CVE-2021-31895 is a high-severity memory corruption vulnerability in Siemens RUGGEDCOM M2100, published on 13 Jul 2021. 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 RUGGEDCOM i800 (All versions < V4.3.7), RUGGEDCOM i801 (All versions < V4.3.7), RUGGEDCOM i802 (All versions < V4.3.7), RUGGEDCOM i803 (All versions < V4.3.7), RUGGEDCOM M2100 (All versions < V4.3.7), RUGGEDCOM M2200 (All versions < V4.3.7), RUGGEDCOM M969 (All versions < V4.3.7), RUGGEDCOM RMC30 (All versions < V4.3.7), RUGGEDCOM RMC8388 V4.X (All versions < V4.3.7), RUGGEDCOM RMC8388 V5.X (All versions < V5.5.4), RUGGEDCOM RP110 (All versions < V4.3.7), RUGGEDCOM RS1600 (All versions < V4.3.7), RUGGEDCOM RS1600F (All versions < V4.3.7), RUGGEDCOM RS1600T (All versions < V4.3.7), RUGGEDCOM RS400 (All versions < V4.3.7), RUGGEDCOM RS401 (All versions < V4.3.7), RUGGEDCOM RS416 (All versions < V4.3.7), RUGGEDCOM RS416P (All versions < V4.3.7), RUGGEDCOM RS416Pv2 V4.X (All versions < V4.3.7), RUGGEDCOM RS416Pv2 V5.X (All versions < V5.5.4), RUGGEDCOM RS416v2 V4.X (All versions < V4.3.7), RUGGEDCOM RS416v2 V5.X (All versions < 5.5.4), RUGGEDCOM RS8000 (All versions < V4.3.7), RUGGEDCOM RS8000A (All versions < V4.3.7), RUGGEDCOM RS8000H (All versions < V4.3.7), RUGGEDCOM RS8000T (All versions < V4.3.7), RUGGEDCOM RS900 (32M) V4.X (All versions < V4.3.7), RUGGEDCOM RS900 (32M) V5.X (All versions < V5.5.4), RUGGEDCOM RS900G (All versions < V4.3.7), RUGGEDCOM RS900G (32M) V4.X (All versions < V4.3.7), RUGGEDCOM RS900G (32M) V5.X (All versions < V5.5.4), RUGGEDCOM RS900GP (All versions < V4.3.7), RUGGEDCOM RS900L (All versions < V4.3.7), RUGGEDCOM RS900W (All versions < V4.3.7), RUGGEDCOM RS910 (All versions < V4.3.7), RUGGEDCOM RS910L (All versions < V4.3.7), RUGGEDCOM RS910W (All versions < V4.3.7), RUGGEDCOM RS920L (All versions < V4.3.7), RUGGEDCOM RS920W (All versions < V4.3.7), RUGGEDCOM RS930L (All versions < V4.3.7), RUGGEDCOM RS930W (All versions < V4.3.7), RUGGEDCOM RS940G (All versions < V4.3.7), RUGGEDCOM RS969 (All versions < V4.3.7), RUGGEDCOM RSG2100 (All versions < V4.3.7), RUGGEDCOM RSG2100 (32M) V4.X (All versions < V4.3.7), RUGGEDCOM RSG2100 (32M) V5.X (All versions < V5.5.4), RUGGEDCOM RSG2100P (All versions < V4.3.7), RUGGEDCOM RSG2100P (32M) V4.X (All versions < V4.3.7), RUGGEDCOM RSG2100P (32M) V5.X (All versions < V5.5.4), RUGGEDCOM RSG2200 (All versions < V4.3.7), RUGGEDCOM RSG2288 V4.X (All versions < V4.3.7), RUGGEDCOM RSG2288 V5.X (All versions < V5.5.4), RUGGEDCOM RSG2300 V4.X (All versions < V4.3.7), RUGGEDCOM RSG2300 V5.X (All versions < V5.5.4), RUGGEDCOM RSG2300P V4.X (All versions < V4.3.7), RUGGEDCOM RSG2300P V5.X (All versions < V5.5.4), RUGGEDCOM RSG2488 V4.X (All versions < V4.3.7), RUGGEDCOM RSG2488 V5.X (All versions < V5.5.4), RUGGEDCOM RSG907R (All versions < V5.5.4), RUGGEDCOM RSG908C (All versions < V5.5.4), RUGGEDCOM RSG909R (All versions < V5.5.4), RUGGEDCOM RSG910C (All versions < V5.5.4), RUGGEDCOM RSG920P V4.X (All versions < V4.3.7), RUGGEDCOM RSG920P V5.X (All versions < V5.5.4), RUGGEDCOM RSL910 (All versions < V5.5.4), RUGGEDCOM RST2228 (All versions < V5.5.4), RUGGEDCOM RST2228P (All versions < V5.5.4), RUGGEDCOM RST916C (All versions < V5.5.4), RUGGEDCOM RST916P (All versions < V5.5.4). The DHCP client in affected devices fails to properly sanitize incoming DHCP packets. This could allow an unauthenticated remote attacker to cause memory to be overwritten, potentially allowing remote code execution. Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2021-31895? It affects 52 products. Products: Siemens Ruggedcom Ros I800, Siemens Ruggedcom Ros I801, Siemens Ruggedcom Ros I802, Siemens Ruggedcom Ros I803, Siemens Ruggedcom Ros M2100, Siemens Ruggedcom Ros M2200, Siemens Ruggedcom Ros M969, Siemens Ruggedcom Ros Rmc, Siemens Ruggedcom Ros Rmc20, Siemens Ruggedcom Ros Rmc30, Siemens Ruggedcom Ros Rmc40, Siemens Ruggedcom Ros Rmc41, Siemens Ruggedcom Ros Rmc8388, Siemens Ruggedcom Ros Rp110, Siemens Ruggedcom Ros Rs400, Siemens Ruggedcom Ros Rs401, Siemens Ruggedcom Ros Rs416, Siemens Ruggedcom Ros Rs416v2, Siemens Ruggedcom Ros Rs8000, Siemens Ruggedcom Ros Rs8000a and 32 more. ## How do I fix CVE-2021-31895? No fix has been published for CVE-2021-31895 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-31895 being exploited? There is no known exploitation of CVE-2021-31895 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-31895 and fix it if it is affected. What it is: CVE-2021-31895 is a high-severity memory corruption vulnerability in Siemens RUGGEDCOM M2100, published on 13 Jul 2021. 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-2021-31895 in the wild and no public exploit code. Affected product: Siemens RUGGEDCOM M2100. 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-31895/ (Markdown: https://insights.sbomify.com/CVE-2021-31895/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-31895 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-31895 - OSV: https://osv.dev/vulnerability/CVE-2021-31895 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-31895/ Summaries are generated and may contain mistakes; the official description above is the record.