CVE-2023-47335
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 · uneditedInsecure permissions in the setNFZEnable function of Autel Robotics EVO Nano drone v1.6.5 allows attackers to breach the geo-fence and fly into no-fly zones.
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 confidenceThe setNFZEnable function in Autel Robotics EVO Nano drone firmware v1.6.5 lacks proper permission controls, allowing unauthenticated or unauthorized attackers to disable geo-fence restrictions and operate the drone in regulated no-fly zones.
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 data= 1.6.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the firmware version installed on the Autel EVO Nano droneAccess the drone's settings or companion application and locate the firmware version information. On Autel drones, this is typically found in the Settings > About section of the Autel Sky app or through the drone's maintenance interface.Affected if The installed firmware version is exactly 1.6.5, matching the affected version listed in the CVE.
-
Verify the presence of the setNFZEnable functionExamine the firmware binary or API interface for the setNFZEnable function. This may require access to the drone's debug or maintenance interface, or reviewing firmware analysis reports if available.Affected if The setNFZEnable function is present in the firmware build, indicating the vulnerable code path exists.
-
Confirm the drone's geo-fence or No-Fly Zone (NFZ) statusCheck the drone's current geo-fence configuration through the Autel Sky app or flight controller settings. Look for any indication that NFZ enforcement is disabled or bypassed.Affected if The geo-fence restriction is found to be disabled or non-functional when it should be active.
-
Inspect network or communication logs for unauthorized setNFZEnable callsIf logging or network capture is available, review logs for any setNFZEnable function calls that may have been invoked, especially from unauthenticated or unexpected sources.Affected if There are logs or evidence of setNFZEnable being called without proper authentication or authorization.
The environment is affected if the Autel EVO Nano drone is running firmware version 1.6.5 and the setNFZEnable function is accessible, allowing geo-fence restrictions to be disabled.
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 dataApply vendor firmware patch when available; until then, implement compensating controls such as restricting drone operation to approved airspace and monitoring for unauthorized firmware modifications.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47335 — 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-2023-47335 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