RVD#3316: No authentication in MAVLink protocol
Published Jul 3, 2020
9.8
CRITICALCVSS 3.1
EPSS 1.76%
Description
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 signing which mitigates this flaw. Another source mentions that MAVLink 2.0 only provides a simple authentication system based on HMAC. This implies that the flying system overall should add the same symmetric key into all devices of network. If not the case, this may cause a security issue, that if one of the devices and its symmetric key are compromised, the whole authentication system is not reliable.
Affected products
- Vendor n/a Product MAVLink Defaultn/a
- Version v1.0StatusaffectedConstraints-
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | MAVLink | n/a |
|
- 1.0.0
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
References (1)
- https://github.com/rligocki/Diploma_thesis_px4 x_refsource_CONFIRMThird Party Advisory
| Link | Providers | Tags |
|---|---|---|
| https://github.com/rligocki/Diploma_thesis_px4 | x_refsource_CONFIRMThird Party Advisory |
Change history (0)
No recorded changes yet.