# CVE-2025-30137: Hardcoded credentials in n/a

> Hardcoded credentials in the G-Net mobile app allow attackers to access dashcam API endpoints and view settings or streams.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-vwgh-xm6c-wqh8

## What is CVE-2025-30137?

CVE-2025-30137 is a critical vulnerability in n/a, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the G-Net GNET APK 2.6.2. Hardcoded credentials exist in in APK for ports 9091 and 9092. The GNET mobile application contains hardcoded credentials that provide unauthorized access to the dashcam's API endpoints on ports 9091 and 9092. Once the GNET SSID is connected to, the attacker sends a crafted authentication command with TibetList and 000000 to list settings of the dashcam at port 9091. There's a separate set of credentials for port 9092 (stream) that is also exposed in cleartext: admin + tibet. For settings, the required credentials are adim + 000000.

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

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


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

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

## Is CVE-2025-30137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30137 is a critical vulnerability in n/a, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30137 in the wild and no public exploit code.

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-30137/ (Markdown: https://insights.sbomify.com/CVE-2025-30137/index.md)
```

## Sources

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

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