Security Resilience

CVE-2025-30112

Auth Bypass

Published
24 March 2025
Modified
15 April 2026
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H
EPSS Score 0.0029 21th percentile
Risk Priority 52 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-30112 is a high-severity Authentication Bypass Using an Alternate Path or Channel (CWE-288) vulnerability in 70Mai (inferred from references). Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique VNC (T1021.005); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-30112 is an authentication bypass vulnerability (CWE-288) affecting 70mai Dash Cam 1S devices, published on 2025-03-24. It enables attackers to circumvent the official mobile app's device authorization mechanism, which requires users to physically press the power button on the device during pairing. By connecting directly to the dashcam's Wi-Fi network and accessing the HTTP API on TCP port 80 or the RTSP service on TCP port 554, attackers can gain unauthorized access without this physical confirmation step.

The vulnerability has a CVSS v3.1 base score of 7.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H), indicating network accessibility with high attack complexity, low privileges required, and no user interaction needed. An attacker who can join the dashcam's network—such as a nearby adversary within Wi-Fi range—can exploit it to bypass pairing restrictions. This grants unauthorized access to the device's API and RTSP video stream, potentially allowing manipulation of settings, live video viewing, or disruption of device functions, with high impacts on integrity and availability alongside limited confidentiality exposure.

Mitigation details are available in referenced advisories, including the security research disclosure at https://github.com/geo-chen/70mai/blob/main/README.md#finding-1---cve-2025-30112-bypass-device-pairing-of-70mai-dashcam-1s and the vendor product page at https://www.70mai.com/cam1s/. Security practitioners should consult these for any firmware updates or configuration hardening recommendations specific to the 70mai Dash Cam 1S.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

a user to physically press on the power button during a connection.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1021.005 VNC Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1556.004 Network Device Authentication Defense Impairment
Adversaries may use [Patch System Image](https://attack.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1559 Inter-Process Communication Execution
Adversaries may abuse inter-process communication (IPC) mechanisms for local code or command execution.
T1674 Input Injection Execution
Adversaries may simulate keystrokes on a victim’s computer by various means to perform any type of action on behalf of the user, such as launching the command interpreter using keyboard shortcuts, typing an inline script to be executed,…
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1313Shared CWE-288
CVE-2026-35087Shared CWE-288
CVE-2024-56325Shared CWE-288
CVE-2026-20460Shared CWE-288
CVE-2024-9930Shared CWE-288
CVE-2025-68711Shared CWE-288
CVE-2025-6688Shared CWE-288
CVE-2024-9989Shared CWE-288
CVE-2024-10490Shared CWE-288
CVE-2026-76943Shared CWE-288

Affected Assets

70Mai
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.4.3
  • V6.6.1
  • V12.1.3

Mitigating Controls (NIST 800-53 r5) AI

Requires a tamperproof, always-invoked reference monitor that structurally blocks bypass via any alternate path.

Enforces authorization checks on every logical access path, eliminating unauthenticated alternate channels.

Mandates unique identification and authentication for all organizational users, covering the primary authentication requirement.

Controls all external and key internal interfaces, reducing the chance of unauthenticated alternate channels.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 full match
blocks

Requiring authentication on every channel and path directly eliminates alternate-path bypasses.

PR.AA-05 mostly match
blocks

Enforcing authorizations and least privilege across all access vectors prevents unauthenticated alternate paths.

PR.IR-01 mostly match
blocks

Protecting networks and environments from unauthorized logical access blocks bypass via undocumented channels.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect alternate-path bypasses but does not prevent them in production.

blocks

A.8.3's core (access restriction per policies, config mechanisms, identity/group controls, isolation, dynamic techniques requiring auth/credentials) directly stops exploitation of alternate unauthenticated paths for most instances; the bounded remainder is non-access-channel cases (e.g. pure logic errors in alternate-path checks) or pre-auth bypasses outside its enforcement scope.

blocks

A.8.5 mandates strong, multi-factor, alternate-path-resistant authentication techniques plus hardened log-on procedures that directly block unauthenticated alternate channels for most cases (e.g. no bypass via weak paths, sniffing, or incomplete checks); the bounded remainder is non-standard or environment-specific alternate channels outside the clause's listed protections.

blocks

Access rights provisioning and review prevent bypass via unmonitored or alternate channels.

blocks

Privileged access rights control reduces risk of bypass through elevated or alternate paths.

prevents

Secure coding practices help avoid bypass vulnerabilities but do not address deployed instances.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248598 There must be no ".shosts" files on the OL 8 operating system. blocks CWE-288
  • V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-288
Oracle Linux 9 (2 rules)
  • V-271757 OL 9 file systems must not contain shosts.equiv files. blocks CWE-288
  • V-271758 OL 9 file systems must not contain .shosts files. blocks CWE-288
RHEL 7 (3 rules)
  • V-204440 Red Hat Enterprise Linux operating systems version 7.2 or newer using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes. blocks CWE-288
  • V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. blocks CWE-288
  • V-204424 The Red Hat Enterprise Linux operating system must not allow accounts configured with blank or null passwords. blocks CWE-288

References