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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-2738 | 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 | Providers |
|---|---|
| https://github.com/aliasrobotics/RVD/issues/3316 |
|
History
No history.
Status: PUBLISHED
Assigner: Alias
Published:
Updated: 2024-09-16T17:08:41.099Z
Reserved: 2020-03-10T00:00:00.000Z
Link: CVE-2020-10283
No data.
Status : Modified
Published: 2020-08-20T09:15:11.140
Modified: 2024-11-21T04:55:08.170
Link: CVE-2020-10283
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD