CVE-2025-2348
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 · uneditedA vulnerability was found in IROAD Dash Cam FX2 up to 20250308. It has been classified as problematic. Affected is an unknown function of the file /mnt/extsd/event/ of the component HTTP/RTSP. The manipulation leads to information disclosure. The attack needs to be initiated within the local network. The exploit has been disclosed to the public and may be used.
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 confidenceThe IROAD Dash Cam FX2 has an information disclosure vulnerability in its HTTP/RTSP interface where the file path /mnt/extsd/event/ can be accessed without proper authentication or authorization. An attacker on the local network can read files stored on the device's external SD card, potentially exposing recorded video files, event logs, or other sensitive data.
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<= 2025-03-08CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IROAD Dash Cam FX2 on the networkScan the local network for devices responding to HTTP or RTSP on common ports (80, 443, 554, 8554). Look for IROAD-specific HTTP headers or RTSP banners. Alternatively, check your DHCP lease table or network devices for a dash cam device.Affected if A device with IROAD Dash Cam FX2 characteristics is found on the network and exposes HTTP or RTSP services.
-
Check firmware versionIf you have access to the device's web interface or admin panel, navigate to the settings or status page to view the firmware version. Alternatively, make an HTTP request to the device and inspect any version information returned in headers or response bodies.Affected if The firmware version is <= 2025-03-08 or the version cannot be determined (assume affected if the device is confirmed to be an IROAD FX2.
-
Test unauthenticated access to vulnerable pathUsing a web browser or curl command, navigate to http://[device-ip]/mnt/extsd/event/ or https://[device-ip]/mnt/extsd/event/ without providing any credentials. Check if the directory listing or file content is returned.Affected if The path /mnt/extsd/event/ is accessible without authentication and returns file listings or file contents.
-
Verify HTTP/RTSP interface is enabledConfirm that the device's HTTP service (typically port 80/443) or RTSP service (port 554/8554) is listening and responds to requests. Use a port scanner or attempt to connect to these ports.Affected if The HTTP or RTSP interface is exposed and responding on the network.
The device is affected if it is an IROAD Dash Cam FX2 with firmware <= 2025-03-08 that has its HTTP/RTSP interface enabled and accessible, and the /mnt/extsd/event/ path can be reached without authentication.
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 dataNetwork segmentation and access controls should be implemented to limit exposure to trusted users only. Since this is a firmware vulnerability in a dash cam device, contact IROAD for an official firmware patch and apply it as soon as available.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2348 — 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-2348 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