# CVE-2023-50121: Denial of service in n/a

> An attacker can cause a denial of service in Autel EVO NANO drone flight control firmware, disrupting operations.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2024
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-8qwh-6r32-9v26

## What is CVE-2023-50121?

CVE-2023-50121 is a medium-severity denial of service vulnerability in n/a, published on 6 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Autel EVO NANO drone flight control firmware version 1.6.5 is vulnerable to denial of service (DoS).

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Autelrobotics Evo Nano Drone Firmware.

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

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

## Is CVE-2023-50121 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-47335](https://insights.sbomify.com/CVE-2023-47335/): Security feature bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50121 is a medium-severity denial of service vulnerability in n/a, published on 6 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50121 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-2023-50121/ (Markdown: https://insights.sbomify.com/CVE-2023-50121/index.md)
```

## Sources

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

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