Multiple High‑Severity Vulnerabilities (CVSS 8.8) in Botslab G980H Dashcams Enable Auth Bypass and Device Takeover
What It Is – CISA’s Industrial Control Systems Advisory (ICSA‑26‑267‑01) lists 14 CVEs affecting the Botslab G980H dashcam series. The flaws span authentication bypass, hard‑coded credentials, path‑traversal, and out‑of‑bounds writes, each scored 8.8 (High) on the CVSS v3 scale.
Exploitability – No public exploit code has been released, but the vulnerability descriptions (e.g., “authentication bypass by capture‑replay”) indicate that a skilled attacker could remotely gain privileged device functionality without needing physical access.
Affected Products – Botslab G980H dashcam series:
* 30010_QHG980HN5294SysFW+ (14 listed CVEs)
* 58_QHG980HMCN5291SysFW+ (14 listed CVEs)
Why It Matters for Trust & Control Assurance
- Continuous control monitoring – IoT devices often sit outside traditional asset inventories; a gap here means you cannot demonstrate ongoing assurance that authentication and configuration controls remain effective.
- Defensible audit evidence – Evidence of patched firmware, secure credential management, and log integrity is required to satisfy auditors and regulators when device compromise could expose sensitive operational data.
- Supply‑chain risk posture – The breadth of flaws across a single product line underscores the need for a documented vendor‑risk program that tracks security updates and validates third‑party device hardening.
Recommended Actions
- Inventory all Botslab G980H dashcams in your environment and map them to the affected firmware versions.
- Apply the latest vendor‑provided firmware patches immediately; if patches are unavailable, isolate the devices from critical networks.
- Validate that default or hard‑coded credentials have been replaced and that strong authentication mechanisms are enforced.
- Enable secure logging and monitor for anomalous configuration changes or unauthorized access attempts.
- Update your risk register and vendor‑risk assessments to reflect the new control gaps, and map the remediation steps to the relevant control objective (e.g., “Access Control – Authentication Management”).
Source: CISA Advisory ICSA‑26‑267‑01