dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-30109

MEDIUM · 6.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 →
70/100
Remediation priority · Elevated
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
In the IROAD APK 5.2.5, there are Hardcoded Credentials in the APK for ports 9091 and 9092. The mobile application for the dashcam contains hardcoded credentials that allow an attacker on the local Wi-Fi network to access API endpoints and retrieve sensitive device information, including live and recorded footage.

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 · moderate confidence

The IROAD dashcam mobile application APK version 5.2.5 contains hardcoded credentials embedded in the application code. These credentials provide authentication bypass for API endpoints listening on ports 9091 and 9092, allowing any attacker connected to the same local Wi-Fi network to access sensitive device data including live and recorded video footage.

MitigationThe vendor must remove hardcoded credentials from the application source code and implement proper dynamic authentication mechanisms (e.g., token-based or certificate-based authentication) with secure credential storage. Users should avoid connecting to untrusted Wi-Fi networks and the vendor should push an updated APK.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/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 the installed IROAD dashcam app version
    On Android: Go to Settings > Apps > IROAD Dashcam (or IROAD) and check the version under App Info. On iOS: Go to Settings > IROAD app > Version. Compare the displayed version to 5.2.5.
    Affected if The installed version matches 5.2.5 or falls within an unknown range centered on 5.2.5 where the hardcoded credentials were present.
  2. Verify if API ports 9091 or 9092 are listening and reachable on the dashcam device
    With the mobile app connected to the dashcam Wi-Fi network, open a terminal and run: nmap -p 9091,9092 <dashcam_ip> or telnet <dashcam_ip> 9091 (and 9092). Replace <dashcam_ip> with the IP address of your dashcam on the local network.
    Affected if Ports 9091 or 9092 return open state and accept connections, indicating the vulnerable API service is active.
  3. Confirm the device is on a potentially untrusted network
    Check the Wi-Fi network your mobile device (running the IROAD app) is connected to. Identify if it is a shared, public, or untrusted network where other unknown devices may be present. Use ipconfig (Windows) or ifconfig/ip a (Linux/macOS) to view your current network SSID.
    Affected if The mobile device and dashcam are connected to a Wi-Fi network that is shared with untrusted devices or is an open/public network.
  4. Test for authentication bypass on the API endpoints
    From a system on the same network as the dashcam, attempt to access the API without credentials using curl -v http://<dashcam_ip>:9091/api/endpoint or curl -v http://<dashcam_ip>:9092/api/endpoint (replace with actual API paths if known).
    Affected if The API returns sensitive data (video streams, recordings, device info) without requiring any authentication token or login.

You are affected if the IROAD dashcam app version is 5.2.5, the dashcam API ports 9091/9092 are open and reachable on your local network, and you are connected to a Wi-Fi network where untrusted parties could access those ports without 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

The vendor must remove hardcoded credentials from the application source code and implement proper dynamic authentication mechanisms (e.g., token-based or certificate-based authentication) with secure credential storage. Users should avoid connecting to untrusted Wi-Fi networks and the vendor should push an updated APK.

Have this fixed 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-30109 — 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-30109 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