Vulnerability Description
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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Dronecode | Micro Air Vehicle Link | 1.0.0 |
Related Weaknesses (CWE)
References
- https://github.com/aliasrobotics/RVD/issues/3316ExploitIssue TrackingThird Party Advisory
- https://github.com/aliasrobotics/RVD/issues/3316ExploitIssue TrackingThird Party Advisory
FAQ
What is CVE-2020-10283?
CVE-2020-10283 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 autopi...
How severe is CVE-2020-10283?
CVE-2020-10283 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2020-10283?
Check the references section above for vendor advisories and patch information. Affected products include: Dronecode Micro Air Vehicle Link.