CVE-2020-10283: RVD#3317: MAVLink version handshaking allows for an attacker to bypass authentication

Published Aug 20, 2020

Updated

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 AUTOPILOTVERSION 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.

Affected Software

1 affected component

Dronecode Micro Air Vehicle Link=1.0.0

Event History

Aug 20, 2020

CVE Published

via MITRE·08:15 AM

Data Sourced

via MITRE·08:15 AM

DescriptionSeverityWeakness

Frequently Asked Questions

What is CVE-2020-10283?

CVE-2020-10283 is a vulnerability in the Micro Air Vehicle Link (MAVLink) protocol that allows unauthorized access due to a version negotiation issue.

How severe is CVE-2020-10283?

CVE-2020-10283 has a severity rating of 9.8 (critical).

What software is affected by CVE-2020-10283?

The affected software is Dronecode Micro Air Vehicle Link (MAVLink) version 1.0.0.

How can I fix CVE-2020-10283?

To fix CVE-2020-10283, update the Dronecode Micro Air Vehicle Link (MAVLink) software to a version that includes a patch for the vulnerability.

Where can I find more information about CVE-2020-10283?

You can find more information about CVE-2020-10283 at the following reference: [GitHub](https://github.com/aliasrobotics/RVD/issues/3316)