# CVE-2025-2343: IROAD Dash Cam X5/Dash Cam X6 Device Pairing hard-coded credentials

> Attackers with local network access can exploit hard-coded credentials in IROAD Dash Cam X5/X6 device pairing to bypass security controls.

- **Severity:** High 7.7 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-q753-2hq6-5vff

## What is CVE-2025-2343?

CVE-2025-2343 is a high-severity vulnerability in IROAD Dash Cam X5, published on 16 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in IROAD Dash Cam X5 and Dash Cam X6 up to 20250308. Affected by this vulnerability is an unknown functionality of the component Device Pairing. The manipulation leads to hard-coded credentials. Access to the local network is required for this attack to succeed. The complexity of an attack is rather high. The exploitation appears to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2025-2343?


## How do I fix CVE-2025-2343?

No fix has been published for CVE-2025-2343 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2343 being exploited?

There is no known exploitation of CVE-2025-2343 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2343 and fix it if it is affected.

What it is: CVE-2025-2343 is a high-severity vulnerability in IROAD Dash Cam X5, published on 16 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2343 in the wild and no public exploit code.

Affected product: IROAD Dash Cam X5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2343/ (Markdown: https://insights.sbomify.com/CVE-2025-2343/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2343
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2343
- OSV: https://osv.dev/vulnerability/CVE-2025-2343

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2343/
Summaries are generated and may contain mistakes; the official description above is the record.