# CVE-2025-30132: Other in n/a

> Attackers can register an unowned internal domain used by IROAD Dashcams to intercept traffic and exfiltrate sensitive data via man-in-the-middle attacks.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2025
- **Updated:** 21 Mar 2025
- **Also known as:** GHSA-g38j-p66c-6qhp

## What is CVE-2025-30132?

CVE-2025-30132 is a critical vulnerability in n/a, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on IROAD Dashcam V devices. It uses an unregistered public domain name as an internal domain, creating a security risk. During analysis, it was found that this domain was not owned by IROAD, allowing an attacker to register it and potentially intercept sensitive device traffic. If the dashcam or related services attempt to resolve this domain over the public Internet instead of locally, it could lead to data exfiltration or man-in-the-middle attacks.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-30132 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30132 is a critical vulnerability in n/a, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30132 in the wild and no public exploit code.

Affected product: n/a. 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-30132/ (Markdown: https://insights.sbomify.com/CVE-2025-30132/index.md)
```

## Sources

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

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