| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in UCI IDOL up to 2.12 and classified as problematic. This impacts an unknown function. The manipulation leads to predictable value. This vulnerability is uniquely identified as CVE-2024-45165. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in UCI IDOL up to 2.12. This issue affects an unknown part. The manipulation with an unknown input leads to a predictable value vulnerability. Using CWE to declare the problem leads to CWE-342. An exact value or random number can be precisely predicted by observing previous values. Impacted is confidentiality. The summary by CVE is:
An issue was discovered in UCI IDOL 2 (aka uciIDOL or IDOL2) through 2.12. Data is sent between client and server with encryption. However, the key is derived from the string "(c)2007 UCI Software GmbH B.Boll" (without quotes). The key is both static and hardcoded. With access to messages, this results in message decryption and encryption by an attacker. Thus, it enables passive and active man-in-the-middle attacks.
The advisory is shared at syss.de. The identification of this vulnerability is CVE-2024-45165 since 08/22/2024. The exploitation is known to be difficult. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.9VulDB Meta Temp Score: 3.9
VulDB Base Score: 2.6
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (MITRE): 🔍
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: Predictable valueCWE: CWE-342 / CWE-341 / CWE-200
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
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
08/22/2024 🔍08/22/2024 🔍
08/22/2024 🔍
11/01/2024 🔍
Sources
Advisory: syss.deStatus: Not defined
CVE: CVE-2024-45165 (🔍)
GCVE (CVE): GCVE-0-2024-45165
GCVE (VulDB): GCVE-100-275537
Entry
Created: 08/22/2024 08:00Updated: 11/01/2024 02:24
Changes: 08/22/2024 08:00 (51), 08/23/2024 11:49 (1), 11/01/2024 02:24 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.