# CVE-2022-29945: Information disclosure in n/a

> DJI drones broadcast unencrypted operator location data via AeroScope, allowing attackers to track users without authentication.

- **Severity:** Medium 4.0 (`CVSS:3.1/AC:H/AV:N/A:N/C:L/I:N/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4p4c-8vr2-gvfw

## What is CVE-2022-29945?

CVE-2022-29945 is a medium-severity vulnerability in n/a, published on 29 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DJI drone devices sold in 2017 through 2022 broadcast unencrypted information about the drone operator's physical location via the AeroScope protocol.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2022-29945?

It affects 11 products.


Products: Dji Air 2 Firmware, Dji Air 2s Firmware, Dji Fhantom 4 Pro Firmware, Dji Fpv Firmware, Dji Inspire 2 Firmware, Dji Mavic 3 Firmware, Dji Mini 2 Firmware, Dji Mini Se Firmware, Dji Rc Pro Firmware, Dji Zenmuse X5s Firmware, Dji Zenmuse X7 Firmware.

## How do I fix CVE-2022-29945?

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

## Is CVE-2022-29945 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29945 and fix it if it is affected.

What it is: CVE-2022-29945 is a medium-severity vulnerability in n/a, published on 29 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29945 in the wild and no public exploit code.

Affected product: n/a. 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-2022-29945/ (Markdown: https://insights.sbomify.com/CVE-2022-29945/index.md)
```

## Sources

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

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