EUVD-2026-108990
GHSA-826v-5gj2-v5c8
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect ADB host over USB
-
ExploitObtain unauthenticated adbd shell (uid 2000)
-
ExecutionEscalate privileges to root
-
ImpactFull device compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | In the default shipping configuration the device sets ro.adb.secure=0 (no host-key authorization) with USB ADB enabled, so an attacker with physical USB access obtains an unauthenticated shell as uid 2000 with no interaction or credentials. Network exploitation is NOT possible by default: it requires that ADB over TCP first be enabled out-of-band (e.g. running the shipped /system/bin/adbd_tcp.sh or setting persist.adb.tcp.port 5555), after which the same unauthenticated shell is reachable over the network. Limiting factors: physical USB access is required for the default path; the initial shell is only uid 2000 (a foothold), so reaching root requires a separate privilege-escalation step; versions outside 0.3.9.7-0.6.6.9 are not stated as affected. |
| Impact | Signals conflict on severity and must be read carefully. The input CVSS 4.0 vector is AV:P (physical) giving base 7.0, reflecting the DEFAULT state where only USB ADB is enabled and reachable over USB; the description separately cites a 9.3 figure that applies to the NON-DEFAULT scenario where ADB over TCP has been enabled (via /system/bin/adbd_tcp.sh or 'setprop persist.adb.tcp.port 5555'), which raises the vector to network-reachable. So the same flaw is 7.0 physical by default and ~9.3 network once an operator enables TCP ADB - defenders should classify based on whether TCP ADB is enabled in their fleet. No CISA KEV listing and no EPSS score are provided, so there is no evidence of widespread automated exploitation; the vuln.today Decision label is 'this_week' (not act_now/emergency). The weakness itself is trivial to abuse once reachable (CWE-306 missing authentication, PR:N, AC:L): ro.adb.secure=0 means any connecting host gets an unauthenticated shell as uid 2000 with no host-key authorization. Net assessment: a genuine high-impact foothold flaw, but the default attack path requires physical USB access, which limits mass/remote exploitation and makes this a prioritized-but-not-emergency issue unless TCP ADB is enabled in the environment. |
| Exploit ScenarioDerived | An attacker with physical USB access to a CrystalSky ZS600C connects an ADB host and, because ro.adb.secure=0 and no host-key prompt occurs, immediately receives an unauthenticated shell as uid 2000, then uses that foothold to escalate to root. If the operator has enabled ADB over TCP, the same unauthenticated shell is reachable over the network without physical access. A public technical write-up describing the issue exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
DJI CrystalSky ZS600C firmware 0.3.9.7 through 0.6.6.9 exposes an unauthenticated adbd shell to anyone with physical USB access because the device ships with ro.adb.secure=0 and USB ADB enabled. An attacker can obtain a uid 2000 shell as a foothold for a separate privilege-escalation step to root; ADB over TCP is not enabled by default, but when enabled out-of-band the same unauthenticated shell is reachable over the network. No public exploit was identified at time of analysis and there is no CISA KEV entry; the assessed CVSS 3.1 score is 7.0 (AV:P) because the default path requires physical access, while the reported CVSS 4.0 base score is 9.3.
RemediationAI
No vendor-released patch was identified at time of analysis, so remediation depends on reducing exposure until DJI provides fixed firmware; the public reference is https://cyber-defence-campus.github.io/projects/vulnerabilities/CVE-2026-114357 and the issue is prioritized for action this week. Disable USB ADB when debugging is not actively required and restrict physical access to the device, recognizing that this removes a legitimate maintenance path. Keep ADB over TCP disabled by not running /system/bin/adbd_tcp.sh and not setting persist.adb.tcp.port 5555, because once TCP ADB is enabled the unauthenticated shell becomes network-reachable. Where firmware configuration permits, set ro.adb.secure=1 to require host-key authorization; the trade-off is that only provisioned authorized hosts can connect, which may disrupt existing debugging workflows.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Android Debug Bridge daemon (adbd) provides debugging access over USB and, when configured, TCP. CWE-306 (Missing Authentication for Critical Function) applies here because the shipped configuration sets ro.adb.secure=0, which disables adbd host-key authorization, and USB ADB is enabled by default. The CPE cpe:2.3:a:dji:crystalsky_zs600c:*:*:*:*:*:*:*:* identifies the DJI CrystalSky ZS600C as the affected platform; EUVD lists firmware 0.3.9.7 through 0.6.6.9. Network reachability is a conditional extension, not the default: it appears only after ADB over TCP is enabled via the shipped /system/bin/adbd_tcp.sh or persist.adb.tcp.port 5555. The sources describe a configuration and authentication gap rather than a memory-safety flaw, and the assessed CVSS 3.1 vector AV:P/AC:L/PR:N/UI:N reflects that the default attack path is physical.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/S:P
Default reachable path is USB so AV:P; ro.adb.secure=0 means no authentication so PR:N and AC:L; unauthenticated shell plus root escalation gives full C/I/A:H.
Primary rating from Vendor (NCSC.ch).
CVSS VectorVendor: NCSC.ch
Lifecycle Timeline
3DescriptionCVE.org
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).
Articles & Coverage 1
Executive ViewAI
The DJI CrystalSky ZS600C remote controller, used with DJI drones for commercial and public safety operations, has a high-severity vulnerability that allows an attacker with physical USB access to obtain an unauthenticated shell. This could enable unauthorized control or data exfiltration from devices used in sensitive missions. Leadership should care because compromised field devices could disrupt operations, leak sensitive data, or serve as a foothold for further attacks.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting physical access to devices, disabling USB debugging, keeping ADB over TCP disabled, and monitoring for unauthorized modifications.
Threat Intelligence Overview
NVD
CVE.org
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
Exploit-DB