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.
References
Link | Resource |
---|---|
https://github.com/aliasrobotics/RVD/issues/3316 | Exploit Issue Tracking Third Party Advisory |
https://github.com/aliasrobotics/RVD/issues/3316 | Exploit Issue Tracking Third Party Advisory |
Configurations
History
21 Nov 2024, 04:55
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/aliasrobotics/RVD/issues/3316 - Exploit, Issue Tracking, Third Party Advisory |
Information
Published : 2020-08-20 09:15
Updated : 2024-11-21 04:55
NVD link : CVE-2020-10283
Mitre link : CVE-2020-10283
CVE.ORG link : CVE-2020-10283
JSON object : View
Products Affected
dronecode
- micro_air_vehicle_link
CWE