G Onx FirmwareOperating system · Gnetsystem

CVE-2025-30141

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 on G-Net Dashcam BB GONX devices. One can Remotely Dump Video Footage and the Live Video Stream. It exposes API endpoints on ports 9091 and 9092 that allow remote access to recorded and live video feeds. An attacker who connects to the dashcam's network can retrieve all stored recordings and convert them from JDR format to MP4. Additionally, port 9092's RTSP stream can be accessed remotely, allowing real-time video feeds to be extracted without the owner's knowledge.

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 G-Net Dashcam BB GONX devices expose unauthenticated API endpoints on ports 9091 and 9092 that allow remote retrieval of all stored video recordings (in JDR format, convertible to MP4) and access to live RTSP video streams on port 9092. An attacker with network access to the dashcam can exfiltrate all footage without any authentication.

MitigationImplement authentication and authorization controls on API endpoints ports 9091/9092, disable remote access to these services if not required, and apply network segmentation to restrict access to trusted sources only.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
G Onx FirmwareOperating system
Affected:all versions

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
None
Availability
None

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

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 device model
    Check if the target device is a G-Net Dashcam BB GONX by reviewing device documentation, network inventory, or accessing the device's web interface or system information
    Affected if The device is a G-Net Dashcam BB GONX model
  2. Scan for open ports 9091 and 9092
    Perform a port scan on the target device to determine if ports 9091 and 9092 are accessible. Use a network scanner such as nmap: nmap -p 9091,9092 <target-ip>
    Affected if Ports 9091 and/or 9092 are open and accepting connections
  3. Test API endpoint on port 9091 for authentication
    Send an HTTP request to the API endpoint on port 9091 without providing any credentials. For example: curl http://<device-ip>:9091/api/endpoint or curl http://<device-ip>:9091/
    Affected if The endpoint responds with video data or valid JSON without requiring authentication credentials
  4. Test RTSP stream access on port 9092
    Attempt to connect to the RTSP stream on port 9092 without authentication using an RTSP client or ffmpeg: ffmpeg -i rtsp://<device-ip>:9092/stream <output>
    Affected if The RTSP stream is accessible and video playback begins without any authentication challenge
  5. Verify video file retrieval without auth
    If API endpoints are discovered, attempt to request video file listings or downloads from the API without any authentication headers or tokens
    Affected if Stored video recordings can be retrieved or listed without authentication

A defender is affected if they have a G-Net Dashcam BB GONX device with ports 9091 or 9092 exposed and those endpoints respond without requiring authentication.

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

Implement authentication and authorization controls on API endpoints ports 9091/9092, disable remote access to these services if not required, and apply network segmentation to restrict access to trusted sources only.

Fix this in G Onx Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-30141 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