CVE-2026-114357
Deferred Deferred - Pending Action

Unauthenticated Remote Shell Access in DJI CrystalSky ZS600C Firmware

Vulnerability report for CVE-2026-114357, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-23

Last updated on: 2026-10-23

Assigner: Switzerland Government Common Vulnerability Program

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).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-23
Last Modified
2026-10-23
Generated
2026-10-23
AI Q&A
2026-10-23
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
DJI CrystalSky ZS600C 0.3.9.7

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Missing authentication in the Android Debug Bridge daemon (adbd) on DJI CrystalSky ZS600C firmware versions v0.3.9.7 through v0.6.6.9 allows an attacker to gain an unauthenticated shell with uid 2000. This provides a starting point for further privilege escalation to root access.

Detection Guidance

Check if ADB is enabled on the device by verifying if ro.adb.secure=0 is set and USB ADB is active. For network detection, scan for open TCP port 5555 if ADB over TCP is enabled. Use commands like 'adb devices' to see connected ADB sessions or 'netstat -tuln | grep 5555' to check for listening ports.

Impact Analysis

An attacker could exploit this to gain control over the device, access sensitive data, install malware, or use the device as a pivot point for further attacks. Physical access or network access (if ADB over TCP is enabled) is required.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or sensitive data, violating GDPR and HIPAA requirements for data protection and access control. Organizations may face compliance penalties if such breaches occur.

Mitigation Strategies

Disable ADB over USB and TCP if not needed. Set ro.adb.secure=1 to enforce host key authorization. Update firmware to the latest version if patches are available. Block external access to port 5555 via firewall rules.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-114357. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart