Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect to dashcam WiFi
-
DeliveryIdentify Telnet service on port 23
-
ExploitAuthenticate with default credentials
-
ExecutionUpload malicious payload
-
PersistExecute code with root privileges
-
ImpactExfiltrate footage or establish persistence
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Default credential prevention
|
| Exploitation Conditions | Exploitation requires the attacker to be on the same network segment as the dashcam (adjacent network access per CVSS AV:A). Specifically, the attacker must either be within WiFi range of the vehicle when the dashcam's hotspot is active, or the dashcam must be connected to a shared network accessible to the attacker (such as fleet management WiFi in parking facilities). The Telnet service must be enabled, which is the default configuration. No authentication is effectively required due to default credentials (CVSS PR:N). No user interaction needed (UI:N). Limiting factors: physical proximity requirement (WiFi range typically 30-100 feet), dashcam must be powered on with WiFi enabled, and attacker must know or guess the WiFi SSID if not broadcasting. Vehicles in isolated parking or garages face lower risk than those in public parking structures or fleet yards with multiple network-connected devices. |
| Impact | Real-world risk assessment reveals conflicting signals requiring nuanced interpretation. CVSS 7.4 (High) reflects complete device compromise potential with no authentication barriers. The adjacent network requirement (AV:A) significantly limits exposure compared to internet-facing vulnerabilities - attackers must be within WiFi range of the vehicle or connect to the dashcam's hotspot. Public exploit code exists on GitHub showing concrete exploitation steps for file upload and code execution, elevating practical risk beyond theoretical. However, EPSS 0.18% (40th percentile) indicates security researchers assess low probability of mass exploitation, likely because consumer dashcams represent low-value targets compared to enterprise infrastructure. The vendor's non-responsiveness to disclosure is concerning for long-term risk, as no patch timeline exists. Priority depends heavily on deployment context: fleet vehicles with networked dashcams in parking facilities face higher risk than personal vehicles with isolated dashcam WiFi. Not CISA KEV-listed, suggesting no observed targeting in critical infrastructure or enterprise environments. |
| Exploit ScenarioDerived | An attacker parks within WiFi range of a target vehicle equipped with a 70mai M300 dashcam or connects to the dashcam's open WiFi hotspot (often named '70mai_M300_[serial]'). Using the publicly available GitHub exploit code, they connect to the Telnet service on TCP port 23 using default factory credentials. Once authenticated, the attacker uploads malicious scripts or binaries to the device filesystem and executes them with root privileges, enabling video footage theft, firmware modification for persistent backdoor installation, or using the compromised dashcam as a pivot point to attack other vehicle network components if connected. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Apr 29, 2026
Remote code execution via default Telnet credentials in 70mai M300 dashcam firmware (versions up to 20250611) allows adjacent network attackers to gain full device control without authentication. The vulnerability has public exploit code available on GitHub demonstrating malicious file upload and code execution capabilities. Despite CVSS 7.4 severity and public exploitation techniques, EPSS probability remains low at 0.18% (40th percentile), suggesting limited widespread targeting of consumer dashcam devices, though adjacent network requirement (AV:A) makes this exploitable in shared WiFi environments or vehicle networks.
Earlier versions of this analysis (1)
A vulnerability was found in 70mai M300 up to 20250611 and classified as critical. Affected by this issue is some unknown functionality of the component Telnet Service. The manipulation leads to use o
RemediationAI
No vendor-released patch identified at time of analysis despite early disclosure attempts. Immediate mitigation: disable the Telnet service if device firmware provides this option through settings or configuration file modification (check /etc/inetd.conf or systemd service files if root access possible). If Telnet cannot be disabled, change default credentials immediately through command-line interface - however, without vendor documentation, correct credential modification procedure is unknown and may brick the device. Most effective compensating control: disable the dashcam's WiFi hotspot feature entirely and restrict connectivity to USB-only data transfer when possible, eliminating the adjacent network attack vector. For fleet deployments requiring WiFi connectivity, isolate dashcam networks from other vehicle systems using VLAN segmentation and implement MAC address filtering to allow only authorized management devices. Monitor for unauthorized Telnet connection attempts on TCP port 23. Trade-offs: disabling WiFi eliminates remote file retrieval convenience; credential changes risk device lockout without vendor reset procedure.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The 70mai M300 is a consumer dashcam device running embedded Linux firmware with network connectivity features. The Telnet service (TCP port 23) is enabled by default with hardcoded factory credentials, representing CWE-1392 (Use of Default Credentials). Telnet transmits credentials in cleartext and provides direct shell access to the underlying operating system. The CVSS 4.0 vector indicates adjacent network attack vector (AV:A), meaning exploitation requires the attacker to be on the same network segment as the device - typically the dashcam's WiFi hotspot or a connected vehicle network. The CPE identifier cpe:2.3:o:70mai:m300_firmware confirms this affects the device firmware/operating system layer rather than a specific application component.
Know when M300 Firmware gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
A vulnerability was found in 70mai M300 up to 20250611 and classified as critical. Affected by this issue is some unknown functionality of the component Telnet Service. The manipulation leads to use of default credentials. The attack needs to be initiated within the local network. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Executive ViewAI
The 70mai M300 dashcam (firmware through 20250611) contains a remote code execution vulnerability exploitable by attackers on adjacent networks using default credentials, with public exploit code now available. Organizations managing connected vehicle fleets or IoT dashcam deployments face immediate risk of device compromise, data theft, and potential lateral network movement if these devices operate on corporate or shared networks.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable Telnet protocol (TCP port 23) at network firewall/access point level; (2) Isolate dashcam traffic to dedicated VLAN with restricted egress rules; (3) Implement MAC-address filtering on WiFi networks to prevent unauthorized device connections; (4) If web interface is accessible, change default admin credentials immediately; (5) Monitor adjacent network access logs for suspicious connection attempts to dashcam IP addresses; (6) Consider temporary device offline status until firmware patch released or hardware replacement completed.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in M300 Firmware
View allDenial of service in 70mai M300 dashcam firmware up to 20250611 allows an attacker on the local network to crash the dev
Improper authentication in 70mai M300 dashcam firmware up to 20250611 allows local network attackers to access the RTSP
A security vulnerability in 70mai M300 (CVSS 3.1). Risk factors: public PoC available.
Exposed root password via unauthenticated HTTP server in 70mai M300 dashcam firmware up to 20250611 allows local network
EUVD-2025-18959
NVD
CVE.org
EPSS
GitHub
VulDB
Exploit-DB