# CVE-2025-30127: Information disclosure in n/a

> Attackers with weak credentials can download sensitive video and audio recordings from Marbella KR8s Dashcams via specific network ports.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-2454-2h9h-6wx6

## What is CVE-2025-30127?

CVE-2025-30127 is a critical vulnerability in n/a, published on 6 Aug 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 Marbella KR8s Dashcam FF 2.0.8 devices. Once access is gained either by default, common, or cracked passwords, the video recordings (containing sensitive routes, conversations, and footage) are open for downloading by creating a socket to command port 7777, and then downloading video via port 7778 and audio via port 7779.

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

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


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

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

## Is CVE-2025-30127 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30127 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30127 is a critical vulnerability in n/a, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30127 exists.

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-30127/ (Markdown: https://insights.sbomify.com/CVE-2025-30127/index.md)
```

## Sources

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

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