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.
References
Link | Resource |
---|---|
https://github.com/rligocki/Diploma_thesis_px4 | Third Party Advisory |
https://github.com/rligocki/Diploma_thesis_px4 | Third Party Advisory |
Configurations
History
21 Nov 2024, 04:55
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/rligocki/Diploma_thesis_px4 - Third Party Advisory |
Information
Published : 2020-07-03 15:15
Updated : 2024-11-21 04:55
NVD link : CVE-2020-10282
Mitre link : CVE-2020-10282
CVE.ORG link : CVE-2020-10282
JSON object : View
Products Affected
dronecode
- micro_air_vehicle_link
CWE
CWE-306
Missing Authentication for Critical Function