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

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

CVE-2020-10283

The CVE-2020-10283 entry concerns MAVLink, a protocol used for UAV ground control and autopilot communication. The root issue is the version negotiation between GCS and autopilot via AUTOPILOT_VERSION, which can cause an attacker to coerce the autopilot to use MAVLink 1.0, a version without authe...

PT-2020-12032 · Dronecode · Mavlink

Name of the Vulnerable Software and Affected Versions: MAVLink versions prior to 2.0 Description: The issue concerns the negotiation of the MAVLink protocol version between the Ground Control Station GCS and the autopilot. An attacker can manipulate the negotiation process to force the autopilot ...

CVE-2020-10282

The Micro Air Vehicle Link MAVLink protocol presents no authentication mechanism on its version 1.0 nor authorization whichs leads to a variety of attacks including identity spoofing, unauthorized access, PITM attacks and more. According to literature, version 2.0 optionally allows for package...

CVE-2020-10281

This vulnerability applies to the Micro Air Vehicle Link MAVLink protocol and allows a remote attacker to gain access to sensitive information provided it has access to the communication medium. MAVLink is a header-based protocol that does not perform encryption to improve transfer and reception...

CVE-2020-10282

The Micro Air Vehicle Link MAVLink protocol presents no authentication mechanism on its version 1.0 nor authorization whichs leads to a variety of attacks including identity spoofing, unauthorized access, PITM attacks and more. According to literature, version 2.0 optionally allows for package...

Design/Logic Flaw

This vulnerability applies to the Micro Air Vehicle Link MAVLink protocol and allows a remote attacker to gain access to sensitive information provided it has access to the communication medium. MAVLink is a header-based protocol that does not perform encryption to improve transfer and reception...

Authorization

The Micro Air Vehicle Link MAVLink protocol presents no authentication mechanism on its version 1.0 nor authorization whichs leads to a variety of attacks including identity spoofing, unauthorized access, PITM attacks and more. According to literature, version 2.0 optionally allows for package...

CVE-2020-10282 RVD#3316: No authentication in MAVLink protocol

The Micro Air Vehicle Link MAVLink protocol presents no authentication mechanism on its version 1.0 nor authorization whichs leads to a variety of attacks including identity spoofing, unauthorized access, PITM attacks and more. According to literature, version 2.0 optionally allows for package...

CVE-2020-10282

The CVE-2020-10282 entry concerns MAVLink, where version 1.0 has no authentication or authorization, enabling identity spoofing, unauthorized access, and man-in-the-middle-style attacks on MAVLink-based UAV communications. Some sources note MAVLink 2.0 adds a basic authentication mechanism (e.g.,...

CVE-2020-10281

Technical details about CVE-2020-10281 are not publicly provided in the connected documents; available sources summarize MAVLink plain-text transmission leakage, but no concrete affected versions, fixes, or exploitation specifics are present here. Monitor for updates.

CVE-2020-10281 RVD#3315: Cleartext transmission of sensitive information in MAVLink protocol version 1.0 and 2.0

This vulnerability applies to the Micro Air Vehicle Link MAVLink protocol and allows a remote attacker to gain access to sensitive information provided it has access to the communication medium. MAVLink is a header-based protocol that does not perform encryption to improve transfer and reception...