PX4 Autopilot Missing authentication for critical function
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| PX4 | Autopilot | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Px4 | Px4-autopilot |
|
Vendor Solution
PX4 recommends enabling MAVLink 2.0 message signing as the authentication mechanism for all non‑USB communication links. PX4 has published a security hardening guide for integrators and manufacturers at https://docs.px4.io/main/en/mavlink/security_hardening Message signing configuration documentation can be found at https://docs.px4.io/main/en/mavlink/message_signing
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.962% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Px4 autopilot
|
|
| CPEs | cpe:2.3:a:px4:autopilot:1.16.0:*:*:*:*:*:*:* | |
| Vendors & Products |
Px4 autopilot
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Px4
Px4 px4-autopilot |
|
| Vendors & Products |
Px4
Px4 px4-autopilot |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The MAVLink communication protocol does not require cryptographic authentication by default. When MAVLink 2.0 message signing is not enabled, any message -- including SERIAL_CONTROL, which provides interactive shell access -- can be sent by an unauthenticated party with access to the MAVLink interface. PX4 provides MAVLink 2.0 message signing as the cryptographic authentication mechanism for all MAVLink communication. When signing is enabled, unsigned messages are rejected at the protocol level. | |
| Title | PX4 Autopilot Missing authentication for critical function | |
| Weaknesses | CWE-306 | |
| References |
| |
| Metrics |
cvssV3_1
|