Rittal IoT Interface/CMC III Processing Unit Function Call rand generation of predictable numbers or identifiers
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Rittal IoT Interface and CMC III Processing Unit. The affected element is the function rand of the component Function Call Handler. This manipulation causes generation of predictable numbers or identifiers.
This vulnerability appears as CVE-2024-47945. In addition, an exploit is available.
Details
A vulnerability has been found in Rittal IoT Interface and CMC III Processing Unit (version now known) and classified as problematic. Affected by this vulnerability is the function rand of the component Function Call Handler. The manipulation with an unknown input leads to a generation of predictable numbers or identifiers vulnerability. The CWE definition for the vulnerability is CWE-340. The product uses a scheme that generates numbers or identifiers that are more predictable than required. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The weakness was presented by Johannes Kruchem. It is possible to read the advisory at r.sec-consult.com. This vulnerability is known as CVE-2024-47945 since 10/07/2024. The exploitation appears to be difficult. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
It is possible to download the exploit at packetstormsecurity.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.6
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Generation of predictable numbers or identifiersCWE: CWE-340 / CWE-331 / CWE-330
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/07/2024 🔍10/15/2024 🔍
10/15/2024 🔍
10/21/2024 🔍
Sources
Advisory: r.sec-consult.comResearcher: Johannes Kruchem
Status: Not defined
CVE: CVE-2024-47945 (🔍)
GCVE (CVE): GCVE-0-2024-47945
GCVE (VulDB): GCVE-100-280363
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/15/2024 13:13Updated: 10/21/2024 15:28
Changes: 10/15/2024 13:13 (53), 10/21/2024 15:28 (10)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.