CVE-2022-29945
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 · uneditedDJI drone devices sold in 2017 through 2022 broadcast unencrypted information about the drone operator's physical location via the AeroScope protocol.
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 · moderate confidenceDJI AeroScope-equipped drones sold between 2017 and 2022 continuously broadcast unencrypted telemetry data including the operator's GPS coordinates via the AeroScope protocol. This allows any party with a compatible receiver to passively track the physical location of both the drone and its operator without any authentication or encryption barriers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify drone modelCheck the physical drone or flight controller documentation to confirm the exact model (e.g., Mavic 3, Air 2s, Mini 2, etc.)Affected if The model matches one of the affected products: Mavic 3, Rc Pro, Air 2s, Air 2, Mini 2, Mini Se, Fpv, or Phantom 4 Pro
-
Verify AeroScope broadcast statusUse the DJI app or drone settings to check if AeroScope (Remote ID) broadcast is enabled. On most models, this appears as 'Enable Broadcast' or 'AeroScope' in the flight safety or transmission settingsAffected if AeroScope broadcast is turned ON - the drone is actively transmitting unencrypted telemetry
-
Confirm firmware versionOpen DJI Fly app or DJI Assistant 2, connect to the drone, and navigate to the firmware information section to view the current firmware versionAffected if The firmware version has NOT been updated to include AeroScope encryption (note: per vendor, all previous versions were affected; check if a post-2022 update has been applied)
You are affected if you own one of the listed drone models and AeroScope broadcast is enabled, unless you have applied a firmware update that implements encryption for AeroScope communications.
Generated from the published advisory. Verify against your own configuration.
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 dataUsers should apply firmware updates provided by DJI that implement encryption for AeroScope broadcasts. Until updated, operators should be aware that location tracking is possible and consider operational security measures in sensitive areas.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29945 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29945 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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