CVE-2024-56897
Yitechnology Yi Car Dashcam Firmware 3.88
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-56897 is a critical-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Yitechnology Yi Car Dashcam Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — 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-2024-56897 is an improper access control vulnerability (CWE-434) in the HTTP server of YI Car Dashcam firmware version 3.88. The flaw enables unrestricted file downloads and uploads, as well as execution of arbitrary API commands without authentication. These API commands allow unauthorized modifications to device settings, such as disabling recording, disabling sounds, and initiating a factory reset. The issue carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), classifying it as critical.
Remote attackers with network access to the device can exploit this vulnerability with low complexity and no required privileges or user interaction. Successful exploitation grants full control over file operations, potentially exposing sensitive data like video recordings through downloads or introducing malware via uploads. Attackers can also disrupt device functionality by altering settings, rendering the dashcam inoperable for surveillance or evidence collection.
Mitigation details are outlined in researcher disclosures, including the Medium article at https://geochen.medium.com/cve-2024-56897-yi-car-dashcam-39304a4b21b4 and the GitHub repository https://github.com/geo-chen/YI-Smart-Dashcam/, which provide proof-of-concept code and analysis. The product page at https://yitechnology.com.sg/products/dash-camera/ offers device information, though no official patches are referenced in the CVE details. Security practitioners should isolate affected devices and monitor for firmware updates from YI Technology.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4285
Vulnerability Data
Improper access control in the HTTP server in YI Car Dashcam v3.88 allows unrestricted file downloads, uploads, and API commands. API commands can also be made to make unauthorized modifications to the device settings, such as disabling recording, disabling sounds,…
more
factory reset.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Mitigating Controls (NIST 800-53 r5) AI
Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.
Least functionality restricts the file types and automatic processing capabilities the system will accept.
Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.
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.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Hardened configuration baselines can enforce allowed file types and processing rules.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
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.
Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.
Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.
Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.
Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.