IROAD Dash Cam X5/Dash Cam X6 up to 20250308 Device Pairing hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in IROAD Dash Cam X5 and Dash Cam X6 up to 20250308. This issue affects some unknown processing of the component Device Pairing. This manipulation causes hard-coded credentials. The identification of this vulnerability is CVE-2025-2343. The attack needs to be done within the local network. There is no exploit available. The vendor was contacted early about this disclosure but did not respond in any way. It looks like a duplicate CVE-2025-30110 has been assigned to this entry.
Details
A vulnerability classified as critical was found in IROAD Dash Cam X5 and Dash Cam X6 up to 20250308. Affected by this vulnerability is some unknown processing of the component Device Pairing. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-2343. The exploitation appears to be difficult. Access to the local network is required for this attack to succeed. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/18/2025). MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
The vendor was contacted early about this disclosure but did not respond in any way.
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: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
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
03/15/2025 🔍03/15/2025 🔍
03/18/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2025-2343 (🔍)
CVE Duplicate: 🔍
GCVE (CVE): GCVE-0-2025-2343
GCVE (VulDB): GCVE-100-299809
Entry
Created: 03/15/2025 19:27Updated: 03/18/2025 16:13
Changes: 03/15/2025 19:27 (52), 03/16/2025 19:28 (30), 03/18/2025 16:13 (1)
Complete: 🔍
Submitter: geochen
Cache ID: 216:D4D:103
Submit
Accepted
- Submit #516881: IROAD Dashcam X series Authentication Bypass by Primary Weakness (by geochen)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.