Cyber Resilience

CVE-2024-30800

Dronecode Px4 Drone Autopilot 1.14.0

Public PoC
Published
23 April 2024
Modified
30 June 2025
Patch / advisory
View advisory
CVSS Score v3.1 5.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:H
EPSS Score 0.0021 11th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2024-30800 is a medium-severity Improper Handling of Values (CWE-229) vulnerability in Dronecode Px4 Drone Autopilot. Its CVSS base score is 5.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

PX4 Autopilot v.1.14 allows an attacker to fly the drone into no-fly zones by breaching the geofence using flaws in the function.

CWE(s)
CWE-229

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-29460Same product: Dronecode Px4 Drone Autopilot
CVE-2026-32706Same product: Dronecode Px4 Drone Autopilot
CVE-2023-46256Same product: Dronecode Px4 Drone Autopilot
CVE-2024-38951Same product: Dronecode Px4 Drone Autopilot
CVE-2026-32708Same product: Dronecode Px4 Drone Autopilot
CVE-2026-32707Same product: Dronecode Px4 Drone Autopilot
CVE-2024-38952Same product: Dronecode Px4 Drone Autopilot
CVE-2026-32705Same product: Dronecode Px4 Drone Autopilot
CVE-2024-40427Same product: Dronecode Px4 Drone Autopilot
CVE-2026-32743Same product: Dronecode Px4 Drone Autopilot

Affected Assets

dronecode
px4 drone autopilot
1.14.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly enforces correct handling of parameter counts and defined values before processing occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input validation and parameter handling to prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing-value flaws but does not itself implement the handling logic.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes input validation and parameter handling requirements that reduce missing-value errors.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for validation of all input parameters and fields.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage robust input handling but do not directly specify value-count checks.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate proper handling of missing or undefined parameters, directly addressing this weakness.

References