CVE-2024-47944: RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit · Missing Protection Mechanism for Alternate Hardware Interface
Affects RITTAL GmbH & Co. KG IoT Interface & CMC III Processing UnitSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 6.21.00.2 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% 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:P/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
1. Upgrade affected devices to firmware version 6.21.00.2 or later as soon as the vendor releases a patch addressing this vulnerability. 2. Restrict physical access to devices by securing server rooms, control cabinets, and other locations where the IoT Interface & CMC III Processing Units are installed. 3. Implement strict network segmentation and access controls to limit network exposure of these devices, especially restricting USB interface access where possible. 4. Monitor device logs and network traffic for unusual firmware upgrade attempts or USB device insertions. 5. Employ endpoint security solutions capable of detecting unauthorized firmware modifications or anomalous device behavior. 6. Establish policies and procedures for secure firmware update processes, including verification of firmware authenticity and integrity before deployment. 7. Conduct regular security audits and penetration testing focused on industrial control systems and IoT devices to identify similar weaknesses. 8. Train staff on the risks associated with physical and network access to critical devices and the importance of following security protocols.
Description
The device directly executes .patch firmware upgrade files on a USB stick without any prior authentication in the admin interface. This leads to an unauthenticated code execution via the firmware upgrade function.