Vehicle Management System 7.31.0.3_20230412 login.html default password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Vehicle Management System 7.31.0.3_20230412 and classified as problematic. This issue affects some unknown processing of the file login.html. The manipulation leads to an unknown weakness. This vulnerability is documented as CVE-2024-30802. There is not any exploit available.
Details
A vulnerability was found in Vehicle Management System 7.31.0.3_20230412. It has been rated as problematic. This issue affects an unknown part of the file login.html. Using CWE to declare the problem leads to CWE-1393. The product uses default passwords for potentially critical functionality. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue in Vehicle Management System 7.31.0.3_20230412 allows an attacker to escalate privileges via the login.html component.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-30802 since 03/27/2024. Technical details are known, but no exploit is available.
By approaching the search of inurl:login.html it is possible to find vulnerable targets with Google Hacking.
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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector: 🔍
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: Default passwordCWE: CWE-1393
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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/27/2024 🔍05/10/2024 🔍
05/10/2024 🔍
09/07/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-30802 (🔍)
GCVE (CVE): GCVE-0-2024-30802
GCVE (VulDB): GCVE-100-263861
Entry
Created: 05/10/2024 17:41Updated: 09/07/2024 01:50
Changes: 05/10/2024 17:41 (49), 09/07/2024 01:50 (13)
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.