Vulnerability in Dronecode Micro Air Vehicle Link
CVE-2020-10283
The Micro Air Vehicle Link (MAVLink) protocol presents authentication mechanisms on its version 2.0 however according to its documentation, in order to maintain backwards compatibility, GCS and autopilot negotiate the version via the AUTOPILOT_VERSION message. Since this negotiation depends on the answer, an attacker may craft packages in a way that hints the autopilot to adopt version 1.0 of MAVLink for the communication. Given the lack of authentication capabilities in such version of MAVLink (refer to CVE-2020-10282), attackers may use this method to bypass authentication capabilities and interact with the autopilot directly.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.015, 74.2th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Dronecode Micro Air Vehicle Link — versions 1.0.0
- Px4 Mavlink — versions 2.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (Live-Hack-CVE/CVE-2020-10283). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/aliasrobotics/RVD/issues/3316 (Exploit, Third Party Advisory, Issue Tracking)