IoT Interface & CMC III Processing Unit: Insufficient Entropy
CVE-2024-47945 is a critical-severity insufficient entropy vulnerability in IoT Interface & CMC III Processing Unit from RITTAL GmbH & Co. KG, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 6.21.00.2 as the first without the flaw, so updating IoT Interface & CMC III Processing Unit to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.87% chance of exploitation within 30 days, higher than 59% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update IoT Interface & CMC III Processing Unit to 6.21.00.2 or a later version.
- Update IoT Interface Firmware to 6.21.00.2 or a later version.
- Update Cmc Iii Processing Units Firmware to 6.21.00.2 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| RITTAL GmbH & Co. KG | IoT Interface & CMC III Processing Unit | <6.21.00.2; before 6.21.00.2 | 6.21.00.2 |
| Rittal | IoT Interface Firmware | before 6.21.00.2 | 6.21.00.2 |
| Rittal | Cmc Iii Processing Units Firmware | before 6.21.00.2 | 6.21.00.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.1 | 9.1 | Critical | CISA (ADP) |
Official description
The devices are vulnerable to session hijacking due to insufficient entropy in its session ID generation algorithm. The session IDs are predictable, with only 32,768 possible values per user, which allows attackers to pre-generate valid session IDs, leading to unauthorized access to user sessions. This is not only due to the use of an (insecure) rand() function call but also because of missing initialization via srand(). As a result only the PIDs are effectively used as seed.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficient Entropy
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
How developers prevent this class of flaw
- Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- r.sec-consult.com/rittaliotExploit, Third Party Advisory
Other references
Other vulnerabilities in IoT Interface & CMC III Processing Unit
- 9.8 Critical severity
Recent Insufficient Entropy vulnerabilities
- 8.2 High severity
- 8.0 High severity
- 9.8 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
- 7.5 High severity
Spotted an error? Tell us.