{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10282 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10282 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10282 is a critical missing authorization vulnerability in unspecified MAVLink, published on 3 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-10282 and fix it if it is affected.\n\nWhat it is: CVE-2020-10282 is a critical missing authorization vulnerability in unspecified MAVLink, published on 3 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-10282 in the wild and no public exploit code.\n\nAffected product: unspecified MAVLink. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-10282/ (Markdown: https://insights.sbomify.com/CVE-2020-10282/index.md)","id":"CVE-2020-10282","markdown":"https://insights.sbomify.com/CVE-2020-10282/index.md","name":"CVE-2020-10282","record":{"aliases":["GHSA-cjmc-hc9f-gvg8"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MAVLink protocol","requires_auth":"none","summary":"The MAVLink protocol lacks authentication, allowing attackers to spoof identities and gain unauthorized access to drone systems.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Alias","cpe":[{"product":"micro_air_vehicle_link","vendor":"dronecode"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"RVD#3316: No authentication in MAVLink protocol","id":"CVE-2020-10282","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"RVD#3317: MAVLink version handshaking allows for an attacker to bypass authentication","id":"CVE-2020-10283"},"packages":[],"prev":{"headline":"RVD#3315: Cleartext transmission of sensitive information in MAVLink protocol version 1.0 and 2.0","id":"CVE-2020-10281"},"products":["MAVLink"],"published":"2020-07-03","related":[{"cvss_score":8.1,"headline":"RVD#3317: MAVLink version handshaking allows for an attacker to bypass authentication","id":"CVE-2020-10283","kev_date_added":null,"published":"2020-08-20"},{"cvss_score":7.5,"headline":"RVD#3315: Cleartext transmission of sensitive information in MAVLink protocol version 1.0 and 2.0","id":"CVE-2020-10281","kev_date_added":null,"published":"2020-07-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["unspecified"]},"summary":"The MAVLink protocol lacks authentication, allowing attackers to spoof identities and gain unauthorized access to drone systems.","url":"https://insights.sbomify.com/CVE-2020-10282/"}