CVE-2019-3945
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 · uneditedWeb 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.
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 Parrot ANAFI drone's embedded web server can be crashed via a denial-of-service vulnerability. The issue occurs when the SDK command 'Common_CurrentDateTime' is sent to the control service with a date length value that exceeds expected bounds, indicating insufficient input validation on the date parameter.
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.5.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Confirm you have a Parrot ANAFI droneIdentify the device on your network or physically inspect for Parrot ANAFI branding. The drone exposes a web server typically accessible via its WiFi IP address (often 192.168.1.1).Affected if The device is a Parrot ANAFI drone with an accessible web interface.
-
Retrieve the installed firmware versionAccess the drone's web interface or use the Parrot FreeFlight6 mobile app to check the firmware version. Alternatively, connect to the drone's WiFi and navigate to the device info page (often at http://192.168.1.1).Affected if The displayed firmware version is below 1.5.0 (e.g., 1.4.x, 1.3.x, etc.).
-
Verify the web control service is activeConfirm the drone's embedded web server is running by accessing http://<drone_ip> in a browser or using curl to check for an HTTP response.Affected if The web interface responds, indicating the Common_CurrentDateTime command handler is exposed.
-
Confirm version is within vulnerable rangeCompare your installed firmware version against the affected range: any version less than 1.5.0.Affected if Firmware version < 1.5.0 AND the web control service is accessible.
You are affected if you own a Parrot ANAFI drone running firmware version less than 1.5.0 with the web server interface enabled.
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 data1.5.0
Apply vendor-supplied firmware updates from Parrot that address input validation in the Common_CurrentDateTime command handler. If no update is available, consider network segmentation to restrict access to the drone's web server interface.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3945 — 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-2019-3945 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