dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-30137

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GNET mobile application (APK 2.6.2) contains hardcoded credentials embedded in the APK that expose the dashcam's API endpoints on ports 9091 and 9092. Port 9091 (settings) uses credentials 'adim' + '000000' while port 9092 (stream) uses 'admin' + 'tibet'. An attacker connected to the GNET SSID can send crafted authentication commands with these credentials to access and list dashcam settings or stream content without authorization.

MitigationRemove hardcoded credentials from the APK and implement dynamic authentication mechanisms such as secure credential storage, certificate-based authentication, or session-based token authentication with proper credential rotation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GNET app installation and version
    Check if the G-Net GNET mobile application is installed on the device. On Android, use Settings > Apps > GNET to view the version number, or run: adb shell dumpsys package com.gnet.app | grep versionName
    Affected if The installed version is v2.6.2 or falls within the affected range around this version
  2. Extract and inspect APK for hardcoded credentials
    Extract the APK from the device (adb pull /data/app/*/base.apk) or obtain it from the source. Use strings, grep, or a hex editor to search for the credential patterns 'adim/000000' and 'admin/tibet' within the binary
    Affected if Either credential pair 'adim/000000' or 'admin/tibet' is found embedded in the APK binary
  3. Check for exposed API ports on GNET device
    If you have access to the GNET dashcam device on the network, scan for open ports 9091 and 9092 using nmap or netcat: nmap -p 9091,9092 <dashcam_ip> or nc -zv <dashcam_ip> 9091 9092
    Affected if Ports 9091 (settings) or 9092 (stream) are open and accessible on the GNET device
  4. Test authentication with hardcoded credentials
    Attempt to authenticate to the exposed API endpoints using curl or similar tool. For settings (port 9091): curl -u adim:000000 http://<dashcam_ip>:9091/api/settings. For stream (port 9092): curl -u admin:tibet http://<dashcam_ip>:9092/api/stream
    Affected if Authentication succeeds with either 'adim/000000' on port 9091 or 'admin/tibet' on port 9092, granting access to dashcam settings or stream

A user is affected if the GNET mobile application v2.6.2 is installed and the hardcoded credentials 'adim/000000' or 'admin/tibet' are present in the APK or successfully authenticate to accessible ports 9091 or 9092 on the GNET device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove hardcoded credentials from the APK and implement dynamic authentication mechanisms such as secure credential storage, certificate-based authentication, or session-based token authentication with proper credential rotation.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30137 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30137 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data