# CVE-2024-33844: Denial of service in n/a

> An attacker can disconnect a Parrot ANAFI USA drone from its controller by sending a malformed MAVLink MISSION_COUNT command, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-fxqv-fm95-w2rw

## What is CVE-2024-33844?

CVE-2024-33844 is a high-severity denial of service vulnerability in n/a, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 'control' in Parrot ANAFI USA firmware 1.10.4 does not check the MAV_MISSION_TYPE(0, 1, 2, 255), which allows attacker to cut off the connection between a controller and the drone by sending MAVLink MISSION_COUNT command with a wrong MAV_MISSION_TYPE.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2024-33844?

It affects 1 product.


Products: Parrot Anafi Firmware.

## How do I fix CVE-2024-33844?

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

## Is CVE-2024-33844 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-3944](https://insights.sbomify.com/CVE-2019-3944/): Denial of service in Parrot ANAFI (high 7.5)
- [CVE-2019-3945](https://insights.sbomify.com/CVE-2019-3945/): Denial of service in Parrot ANAFI (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33844 and fix it if it is affected.

What it is: CVE-2024-33844 is a high-severity denial of service vulnerability in n/a, published on 3 May 2024. 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-2024-33844 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-2024-33844/ (Markdown: https://insights.sbomify.com/CVE-2024-33844/index.md)
```

## Sources

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

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