CISA Lists 14 Botslab Dashcam Flaws With No Fix in Sight
Security / news
CISA Lists 14 Botslab Dashcam Flaws With No Fix in Sight
The worst of the bugs lets a network attacker push firmware with no cryptographic signature onto the device, and Botslab has not told CISA whether it plans to fix any of the 14.
CISA published 14 vulnerabilities in the firmware of Botslab's G980H dashcam on Sept. 24, and the advisory that lists them says the manufacturer has not engaged with the agency on fixing any. No patched firmware version exists for either affected build, and CISA's own guidance is limited to isolating the devices on a network rather than updating them.
The flaws span two firmware families sold under the G980H name, tracked internally by Botslab as 30010_QHG980HN5294SysFW+ and 58_QHG980HMCN5291SysFW+. Thirteen of the 14 apply to both; the 14th, CVE-2026-79959, a hard-coded root password that cannot be changed, is specific to the 30010 build.
The score that matters most here
The highest-rated flaw, CVE-2026-81630, scores 8.1 under CVSS 3.1 but 9.2, a critical rating, under CISA's newer CVSS 4.0 metric. The bug is in how the dashcam checks its own firmware updates: the device fetches new firmware over an unprotected connection and verifies it against an integrity value bundled with the download rather than a cryptographic signature it cannot forge. An attacker positioned on the same network as the device during an update can substitute their own firmware, and the dashcam has no way to tell the difference.
Three more bugs cluster around session handling. CVE-2026-84399 lets an attacker guess a valid session identifier because the values are drawn from a small, sequential range rather than a random one. CVE-2026-82566 lets a terminated session's authentication state stay valid after the legitimate client disconnects. CVE-2026-77967 accepts a captured authentication value a second time without checking whether it has already been used. Each carries a CVSS 3.1 score of 8.1 to 8.8, and each requires only that an attacker share network access with the camera, not physical possession of it.
The bugs that need a screwdriver, not a network
Two flaws require physical or short-range access instead. CVE-2026-88956 exposes a root account with no password over the device's UART hardware interface, the serial connection used for diagnostics, and prints the device's Wi-Fi password to that interface on startup. CVE-2026-84403 lets anyone within Bluetooth range connect to the camera's Bluetooth Low Energy interface without pairing, which is enough to retrieve the same Wi-Fi credentials.
| CVE | CVSS 3.1 | Flaw |
|---|---|---|
| CVE-2026-81630 | 8.1 | Firmware updates accepted without a cryptographic signature |
| CVE-2026-84399 | 8.8 | Session identifiers guessable from a small numeric range |
| CVE-2026-82566 | 8.8 | Session stays valid after the client disconnects |
| CVE-2026-77967 | 8.1 | Captured authentication values accepted a second time |
| CVE-2026-88956 | 6.8 | Passwordless root account reachable over UART |
No patch, and no answer from the vendor
CISA's advisory states plainly that Botslab has not responded to the agency's attempts to coordinate a fix. Botslab's own security-advisory page, checked Sept. 26, says the company will "release the formal security advisory" once a reported issue is confirmed and fixed. Two days after CISA's disclosure, that page carries no mention of any of the 14 CVE identifiers, and no firmware update addressing them is listed on Botslab's site.
The researcher CISA credits with finding the bugs is identified in the advisory only as Julian, of Software Secured, an Ottawa-based firm whose chief executive and founder, Sherif Koussa, describes it on the company's own site as a manual penetration-testing shop for business software vendors. CISA has not said whether Software Secured found the flaws during a client engagement or independent research.
With no patch available, CISA's mitigation advice is defensive rather than corrective: isolate the dashcam's network segment behind a firewall, minimize its exposure to the open internet, and use a VPN for any remote access rather than exposing the device's web interface directly. Network isolation, firewalls and a VPN for remote access is advice aimed at reducing exposure, not at fixing anything. It is the same category of unresolved hardware disclosure as a Hitachi Energy platform CISA rated 9.9 with no patch version at all and a universal hard-coded key CISA found in Flock Safety's license-plate cameras. For G980H owners, for now, network isolation is all there is.
Sources
- 03About Us
More in Security
- 01Java4Shell Scores 9.2 From Its Finder and 8.1 From OpenJDK, and Needs an AVX-512 CPUCalif says a 65-character Base64 string overwrites 62 bytes of Java heap and reaches code execution in Keycloak, Jenkins and Jira. A second security firm says the source shows only a crash.
- 02CISA Gave 9 of 16 November KEV Entries a Three-Day Deadline With Forensic Triage, and 7 Got 14 DaysThe catalog's own due-date and forensicTriage fields show two tiers under BOD 26-04. Sorting November's additions by tier shows which exploited bugs CISA treats as already-compromised-until-proven-otherwise.
- 03Project Zero Cuts Its Disclosure Deadline to 60 Days on Feb. 2, 2027, Then 30 in 2028Google's bug-hunting team is dropping the 30-day patch soak period and counting every deadline from the day it reports, citing AI-assisted exploitation.
- 04Google Finds exploit_agent Diffing Patches and Firing Exploits With No Operator in the LoopGTIG's November 16 tracker reports the first fully automated discovery-to-exploit pipeline it has seen, found on an exposed staging server, plus 22 zero-days in August.