CVE-2024-47943: RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit · Improper Verification of Cryptographic Signature
Affects RITTAL GmbH & Co. KG IoT Interface & CMC III Processing UnitSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 6.21.00.2 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.21.00.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit to 6.21.00.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit | Affected
| Fixed in
|
AI-suggested
To mitigate the risks posed by CVE-2024-47943, European organizations should implement the following specific measures: 1) Immediately identify all RITTAL IoT Interface and CMC III Processing Unit devices in their environment and verify firmware versions; prioritize upgrading to version 6.21.00.2 or later once the vendor releases a patch. 2) Until patches are applied, isolate affected devices on segmented networks with strict firewall rules to limit exposure to untrusted networks and reduce attack surface. 3) Restrict access to the administrative web interface using strong authentication mechanisms, VPNs, and IP whitelisting to prevent unauthorized firmware uploads. 4) Monitor network traffic and device logs for unusual firmware upgrade attempts or unexpected patch file uploads. 5) Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation attempts targeting this vulnerability. 6) Engage with RITTAL support and subscribe to security advisories to receive timely updates and guidance. 7) Implement a robust incident response plan tailored to industrial control system compromises, including device isolation and forensic analysis. 8) Consider deploying application allowlisting or integrity verification mechanisms on devices to detect unauthorized code execution. These targeted actions go beyond generic patching advice and focus on reducing exposure and enhancing detection capabilities specific to this vulnerability.
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.