# CVE-2025-2348: IROAD Dash Cam FX2 HTTP/RTSP event information disclosure

> An attacker on the local network can access event information from the IROAD Dash Cam FX2 via HTTP/RTSP interfaces.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-x83r-m463-jfj9

## What is CVE-2025-2348?

CVE-2025-2348 is a medium-severity vulnerability in IROAD Dash Cam FX2, published on 16 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A 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.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-2348?

It affects 1 product.


Products: Iroadau Fx2 Firmware.

## How do I fix CVE-2025-2348?

No fix has been published for CVE-2025-2348 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2348 being exploited?

There is no known exploitation of CVE-2025-2348 in the wild and no public exploit code.

## Other vulnerabilities in IROAD Dash Cam FX2

- [CVE-2025-30133](https://insights.sbomify.com/CVE-2025-30133/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-30131](https://insights.sbomify.com/CVE-2025-30131/): File upload in n/a (critical 9.8)
- [CVE-2025-30135](https://insights.sbomify.com/CVE-2025-30135/): Missing authorization in n/a (critical 9.4)
- [CVE-2025-2347](https://insights.sbomify.com/CVE-2025-2347/): IROAD Dash Cam FX2 Device Registration default password (medium 5.3)
- [CVE-2025-2350](https://insights.sbomify.com/CVE-2025-2350/): IROAD Dash Cam FX2 upload_file unrestricted upload (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2348 and fix it if it is affected.

What it is: CVE-2025-2348 is a medium-severity vulnerability in IROAD Dash Cam FX2, published on 16 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2348 in the wild and no public exploit code.

Affected product: IROAD Dash Cam FX2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2348/ (Markdown: https://insights.sbomify.com/CVE-2025-2348/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2348
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2348
- OSV: https://osv.dev/vulnerability/CVE-2025-2348

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2348/
Summaries are generated and may contain mistakes; the official description above is the record.