DJI Drone HTTP Media Server Allows Unauthenticated Access to Stored Media
DJI Neo · DJI Neo 2 · DJI Flip · DJI Air 3
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| DJI Neo |
| No fix yet |
| DJI Neo 2 |
| No fix yet |
| DJI Flip |
| No fix yet |
| DJI Air 3 |
| No fix yet |
| DJI Air 3S |
| No fix yet |
| DJI Avata 2 |
| No fix yet |
| DJI Avata 360 |
| No fix yet |
| DJI Mavic 3 |
| No fix yet |
| DJI Mavic 3 Classic |
| No fix yet |
| DJI Mavic 3 Pro |
| No fix yet |
| DJI Mavic 4 Pro |
| No fix yet |
| DJI Mini 2 |
| No fix yet |
| DJI Mini 3 |
| No fix yet |
| DJI Mini 3 Pro |
| No fix yet |
| DJI Mini 4 Pro |
| No fix yet |
| DJI Mini 5 Pro |
| No fix yet |
Original description
The HTTP media server running on DJI drones serves stored photos and videos through the `/v2` endpoint without authenticating the requesting client. Filenames follow a predictable pattern, allowing an attacker who joins the drone's internal network to enumerate valid filenames and exfiltrate stored photos and videos. The exposed media may reveal sensitive information, including private locations, property, travel history, identifiable individuals, and the operator's routines.
Affected models are DJI Neo until 01.00.0400, DJI Neo 2 until 01.00.0500, DJI Flip until 01.00.1200, DJI Air 3 until 01.00.1600, DJI Air 3S until 01.00.1400, DJI Avata 2 until 01.00.0400, DJI Avata 360 until 01.00.0300, DJI Mavic 3 until 01.00.1400, DJI Mavic 3 Classic until 01.00.0800, DJI Mavic 3 Pro until 01.01.0700, DJI Mavic 4 Pro until 01.00.0500, DJI Mini 2 until 01.07.0200, DJI Mini 3 until 01.00.0500, DJI Mini 3 Pro until 01.00.0900, DJI Mini 4 Pro until 01.00.1100, and DJI Mini 5 Pro until 01.00.0600.
From the CVE record · CIRCL