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

> Attackers can execute arbitrary code on Rittal IoT devices by crafting malicious firmware patches using a hard-coded HMAC key.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2024
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-3ggr-5p57-2xgh

## What is CVE-2024-47943?

CVE-2024-47943 is a critical vulnerability in RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2024-47943?


## How do I fix CVE-2024-47943?

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

## Is CVE-2024-47943 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47943 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47943 and fix it if it is affected.

What it is: CVE-2024-47943 is a critical vulnerability in RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47943 exists.

Affected product: RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit. 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-2024-47943/ (Markdown: https://insights.sbomify.com/CVE-2024-47943/index.md)
```

## Sources

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

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