# CVE-2019-3945: Denial of service in Parrot ANAFI

> An attacker can crash the Parrot ANAFI drone's web server by sending a malformed date 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:** 1 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qmj3-mf2v-mhvg

## What is CVE-2019-3945?

CVE-2019-3945 is a high-severity denial of service vulnerability in Parrot ANAFI, published on 1 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Web server running on Parrot ANAFI can be crashed due to the SDK command "Common_CurrentDateTime" being sent to control service with larger than expected date length.

## Which versions are affected by CVE-2019-3945?

It affects 1 product.


Products: Parrot Anafi Firmware.

## How do I fix CVE-2019-3945?

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

## Is CVE-2019-3945 being exploited?

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

## Other vulnerabilities in Parrot ANAFI

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3945 and fix it if it is affected.

What it is: CVE-2019-3945 is a high-severity denial of service vulnerability in Parrot ANAFI, published on 1 Apr 2020. 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-2019-3945 in the wild and no public exploit code.

Affected product: Parrot ANAFI. 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-2019-3945/ (Markdown: https://insights.sbomify.com/CVE-2019-3945/index.md)
```

## Sources

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

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