Submit #928043: Thinkware U3000 up to 1.02.04 Improper Access Controlsinfo

TitelThinkware U3000 up to 1.02.04 Improper Access Controls
BeschreibungThinkware U3000 dashcam, firmware up to and including v1.02.04. The device's local TCP control protocol (command socket 7878, data socket 8787) has no authentication of any kind. Two commands, LS (msg_id 1282) and GET_FILE (msg_id 1285), list and read the contents of any absolute path on the device's filesystem with no restriction. Any device on the same local network as the camera can complete the protocol's session handshake (no credentials required) and then use LS and GET_FILE to enumerate and read arbitrary files, not just recorded video. Verified by reading /tmp/wpa_supplicant.conf directly from the device, which contains the camera's real WiFi SSID and plaintext password for the network it is joined to. LS on /tmp confirmed the file was present alongside other real system files. GET_FILE returned the full file content over the data socket. Confirmed on firmware v1.02.00 and re-confirmed after upgrading to the current production release, v1.02.04; behavior is identical on both. Reported to Thinkware via [email protected] on 2026-06-21. Acknowledged the next business day with no technical response. No fix confirmed as of public disclosure.
Quelle⚠️ https://github.com/turretsec/disclosure-thinkware-u3000/blob/main/findings/02-arbitrary-file-read.md
Benutzer
 turret (UID 100496)
Einreichung13.08.2026 19:21 (vor 2 Monaten)
Moderieren27.09.2026 18:29 (1 month later)
StatusAkzeptiert
VulDB Eintrag410916 [Thinkware U3000 bis 1.02.04 TCP Service /tmp/wpa_supplicant.conf get_file erweiterte Rechte]
Punkte20

Do you want to use VulDB in your project?

Use the official API to access entries easily!