| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in e-trust Horacius 1.0/1.1/1.2. This vulnerability affects unknown code. Performing a manipulation results in password recovery. This vulnerability was named CVE-2024-29417. The attack needs to be approached locally. There is no available exploit.
Details
A vulnerability was found in e-trust Horacius 1.0/1.1/1.2. It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a password recovery vulnerability. CWE is classifying the issue as CWE-640. The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. This is going to have an impact on integrity. The summary by CVE is:
Insecure Permissions vulnerability in e-trust Horacius 1.0, 1.1, and 1.2 allows a local attacker to escalate privileges via the password reset function.
The advisory is shared at blog.pridesec.com.br. This vulnerability is uniquely identified as CVE-2024-29417 since 03/19/2024. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
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: Password recoveryCWE: CWE-640
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
03/19/2024 🔍05/03/2024 🔍
05/03/2024 🔍
05/03/2024 🔍
Sources
Advisory: blog.pridesec.com.brStatus: Not defined
CVE: CVE-2024-29417 (🔍)
GCVE (CVE): GCVE-0-2024-29417
GCVE (VulDB): GCVE-100-263013
Entry
Created: 05/03/2024 17:28Changes: 05/03/2024 17:28 (50)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.