# CVE-2025-2119: Thinkware Car Dashcam F800 Pro Device Registration default credentials

> Attackers with physical access can use default credentials to bypass authentication and take over the Thinkware Car Dashcam F800 Pro device.

- **Severity:** Low 1.0 (`CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** 9 Mar 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-37pf-3g8r-x352

## What is CVE-2025-2119?

CVE-2025-2119 is a low-severity vulnerability in Thinkware Car Dashcam F800 Pro, published on 9 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been declared as problematic. This vulnerability affects unknown code of the component Device Registration Handler. The manipulation leads to use of default credentials. It is possible to launch the attack on the physical device. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2025-2119 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2119 is a low-severity vulnerability in Thinkware Car Dashcam F800 Pro, published on 9 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-2119 in the wild and no public exploit code.

Affected product: Thinkware Car Dashcam F800 Pro. 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-2119/ (Markdown: https://insights.sbomify.com/CVE-2025-2119/index.md)
```

## Sources

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

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