# CVE-2025-51643: Information disclosure in n/a

> Physical attackers can extract firmware and sensitive credentials from Meitrack GPS trackers via unprotected SPI flash access.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A: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:** 28 Aug 2025
- **Updated:** 28 Aug 2025
- **Also known as:** GHSA-5mh7-cqvw-mcp7

## What is CVE-2025-51643?

CVE-2025-51643 is a low-severity vulnerability in n/a, published on 28 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Meitrack T366G-L GPS Tracker devices contain an SPI flash chip (Winbond 25Q64JVSIQ) that is accessible without authentication or tamper protection. An attacker with physical access to the device can use a standard SPI programmer to extract the firmware using flashrom. This results in exposure of sensitive configuration data such as APN credentials, backend server information, and network parameter

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Meitrack T366l-G Firmware.

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

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

## Is CVE-2025-51643 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51643 exists.

Public exploit code:

- https://github.com/NastyCrow/CVE-2025-51643 (github_poc): https://github.com/NastyCrow/CVE-2025-51643

## Fix prompt for AI coding agents

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

What it is: CVE-2025-51643 is a low-severity vulnerability in n/a, published on 28 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51643 exists.

Affected product: n/a. 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-51643/ (Markdown: https://insights.sbomify.com/CVE-2025-51643/index.md)
```

## Sources

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

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