dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2023-6949

MEDIUM · 5.2 CVSS v3.1 Published 2024-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
52/100
Remediation priority · Moderate

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Missing Authentication for Critical Function issue affecting the HTTP service running on the DJI Mavic Mini 3 Pro on the standard port 80 could allow an attacker to enumerate and download videos and pictures saved on the drone internal or external memory without requiring any kind of authentication.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The DJI Mavic Mini 3 Pro exposes an unauthenticated HTTP service on port 80 that allows remote attackers to enumerate and download videos and pictures stored on the drone's internal or external memory without any authentication credentials.

MitigationDJI should implement proper authentication on the HTTP service. Users should avoid connecting to untrusted networks where the drone's HTTP service may be accessible and apply vendor firmware updates when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model
    Identify if the target device is a DJI Mavic Mini 3 Pro drone. This can be done by checking the device label, firmware information, or by accessing the device's network identity if already connected.
    Affected if The device is a DJI Mavic Mini 3 Pro model
  2. Verify port 80 is exposed
    Perform a port scan against the drone's IP address on port 80 (e.g., using nmap -p 80 <drone-ip> or netcat). The drone must be connected to the same network.
    Affected if Port 80 is open and accepting HTTP connections
  3. Test HTTP service accessibility
    Open a web browser or use curl to navigate to http://<drone-ip>/ without providing any authentication credentials. Observe if a web interface loads.
    Affected if The HTTP service loads without requiring any login or authentication
  4. Check for unauthenticated file access
    Browse the HTTP interface or enumerate common paths (e.g., /, /sdcard/, /storage/) to see if video or picture files can be listed or downloaded without authentication.
    Affected if File listings or media downloads are accessible without any credentials

If the device is a DJI Mavic Mini 3 Pro with port 80 open and the HTTP service grants access to media files without requiring authentication, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

DJI should implement proper authentication on the HTTP service. Users should avoid connecting to untrusted networks where the drone's HTTP service may be accessible and apply vendor firmware updates when available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6949 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data