CVE-2025-30135
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 · uneditedAn issue was discovered on IROAD Dashcam FX2 devices. Dumping Files Over HTTP and RTSP Without Authentication can occur. It lacks authentication controls on its HTTP and RTSP interfaces, allowing attackers to retrieve sensitive files and video recordings. By connecting to http://192.168.10.1/mnt/extsd/event/, an attacker can download all stored video recordings in an unencrypted manner. Additionally, the RTSP stream on port 8554 is accessible without authentication, allowing an attacker to view live 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 · high confidenceThe IROAD Dashcam FX2 lacks authentication on its HTTP and RTSP interfaces. Attackers can directly access http://192.168.10.1/mnt/extsd/event/ to download unencrypted stored video recordings, and connect to the RTSP stream on port 8554 without credentials to view live footage.
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 dataall versionsCVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the dashcam device on the networkScan your local network for devices with an HTTP service, particularly at IP 192.168.10.1 or check device manufacturer via MAC address lookup. Verify the device model is IROAD Dashcam FX2.Affected if The device is confirmed to be an IROAD Dashcam FX2 on the network.
-
Test HTTP interface authentication on the event recording pathAttempt to access http://[device_ip]/mnt/extsd/event/ using a web browser or curl command without providing any login credentials.Affected if The HTTP interface returns a directory listing or allows file downloads without requiring any username or password.
-
Test RTSP stream on port 8554 without credentialsUse an RTSP client (such as VLC media player or ffplay) to connect to rtsp://[device_ip]:8554/ without providing any authentication credentials.Affected if The RTSP stream connects and displays live video footage without prompting for a username or password.
-
Check if network isolation is in placeReview your network segmentation and firewall rules to determine whether the dashcam device is placed on an unrestricted internal network segment accessible by other devices.Affected if The dashcam is on a network segment that allows unrestricted access from other internal hosts, enabling an attacker on the same network to reach the unauthenticated interfaces.
A user is affected if they have an IROAD Dashcam FX2 device accessible on their network where the HTTP interface at /mnt/extsd/event/ or the RTSP stream on port 8554 can be accessed without any authentication credentials.
Generated from the published advisory. Verify against your own configuration.
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 dataIsolate dashcam devices on a restricted network segment behind a firewall; if remote access is required, implement a VPN or authentication proxy. Contact the vendor for firmware updates that may add authentication capabilities.
- Consultation6.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,104.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30135 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30135 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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