# CVE-2025-30112: Auth bypass in n/a

> Attackers can bypass physical button authorization on 70mai Dash Cam 1S devices by directly accessing network APIs, allowing unauthorized device control.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2025
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-77gx-q4qr-rpgr

## What is CVE-2025-30112?

CVE-2025-30112 is a high-severity authentication bypass vulnerability in n/a, published on 24 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On 70mai Dash Cam 1S devices, by connecting directly to the dashcam's network and accessing the API on port 80 and RTSP on port 554, an attacker can bypass the device authorization mechanism from the official mobile app that requires a user to physically press on the power button during a connection.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2025-30112 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30112 is a high-severity authentication bypass vulnerability in n/a, published on 24 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30112 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-30112/ (Markdown: https://insights.sbomify.com/CVE-2025-30112/index.md)
```

## Sources

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

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