Security advisory
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2020-10282
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 05:30 UTC · Revision 1
Source evidence
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.
osv:CVE-2020-10282
Complete source record
{
"id": "2e82f44ff3044fc1d3a03ba06ec26beb93dc43a5e1843294e426f47c54386e2e",
"url": "https://osv.dev/vulnerability/CVE-2020-10282",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2020-10282",
"summary": "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.",
"evidence": "osv:CVE-2020-10282",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2020-10282",
"aliases": [
"CVE-2020-10282"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/mavlink/mavlink",
"type": "GIT",
"events": [
{
"introduced": "f3eb010bfea94fbea50c65b039987d7c5b856e4e"
},
{
"last_affected": "f3eb010bfea94fbea50c65b039987d7c5b856e4e"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:dronecode:micro_air_vehicle_link:1.0.0:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.0.0"
},
{
"last_affected": "1.0.0"
}
],
"source": "CPE_STRING"
}
]
}
}
],
"versions": [
"1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2020-10282.json"
}
}
],
"modified": "2026-10-24T10:30:29.630744902Z",
"provider": "osv",
"references": [
"https://github.com/rligocki/Diploma_thesis_px4"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2020-10282",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 432364,
"published_at": "2020-07-03T15:15:09.87+00:00"
}