DJI CrystalSky ZS600C ships ADB without authentication (ro.adb.secure=0)
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The DJI CrystalSky ZS600C tablet's Android-based firmware is affected, specifically its Android Debug Bridge service, which ships configured to accept shell access without authentication. An attacker with physical USB access, or network access once ADB over TCP is turned on, could gain an unauthenticated shell on the device and use it as a starting point to attempt gaining full administrative (root) control.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Missing authentication for a critical function in the Android Debug Bridge daemon (adbd) in DJI CrystalSky ZS600C firmware v0.3.9.7 through v0.6.6.9 allows an attacker to obtain an unauthenticated shell (uid 2000), a foothold for privilege escalation to root. The device ships with ro.adb.secure=0 (no host key authorization) and USB ADB enabled by default; ADB over TCP is not enabled by default but, once enabled (e.g. via the shipped /system/bin/adbd_tcp.sh or 'setprop persist.adb.tcp.port 5555'), the same unauthenticated shell is reachable over the network (CVSS 4.0 base 9.3).
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- DJI CrystalSky ZS600C
From 0.3.9.7 · through 0.6.6.9