# CVE-2023-6951: A Use of Weak Credentials vulnerability affecting the Wi-Fi network generated by a set of DJI drones could allow a remote attacker to derive


- **Severity:** Medium 6.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Apr 2024
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-f74c-6mfp-rg2q

## What is CVE-2023-6951?

CVE-2023-6951 is a medium-severity vulnerability in DJI Matrice 300, published on 2 Apr 2024. 

### Official description

A Use of Weak Credentials vulnerability affecting the Wi-Fi network generated by a set of DJI drones could allow a remote attacker to derive the WPA2 PSK key and authenticate without permission to the drone’s Wi- Fi network. This, in turn, allows the attacker to perform unauthorized interaction with the network services exposed by the drone and to potentially decrypt the Wi-Fi traffic exchanged between the drone and the Android/IOS device of the legitimate user during QuickTransfer mode. Affected models are Mavic 3 Pro until v01.01.0300, Mavic 3 until v01.00.1200, Mavic 3 Classic until v01.00.0500, Mavic 3 Enterprise until v07.01.10.03, Matrice 300 until v57.00.01.00, Matrice M30 until v07.01.0022 and Mini 3 Pro until v01.00.0620.

Weakness: CWE-334 (Small Space of Random Values)

## Which versions are affected by CVE-2023-6951?


## How do I fix CVE-2023-6951?

No fix has been published for CVE-2023-6951 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-6951 being exploited?

There is no known exploitation of CVE-2023-6951 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6951 and fix it if it is affected.

What it is: CVE-2023-6951 is a medium-severity vulnerability in DJI Matrice 300, published on 2 Apr 2024. 
Exploitation: There is no known exploitation of CVE-2023-6951 in the wild and no public exploit code.

Affected product: DJI Matrice 300. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6951/ (Markdown: https://insights.sbomify.com/CVE-2023-6951/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6951
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6951
- OSV: https://osv.dev/vulnerability/CVE-2023-6951

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6951/
Summaries are generated and may contain mistakes; the official description above is the record.