{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10281 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10281 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10281 is a high-severity 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-10281 and fix it if it is affected.\n\nWhat it is: CVE-2020-10281 is a high-severity 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-10281 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-10281/ (Markdown: https://insights.sbomify.com/CVE-2020-10281/index.md)","id":"CVE-2020-10281","markdown":"https://insights.sbomify.com/CVE-2020-10281/index.md","name":"CVE-2020-10281","record":{"aliases":["GHSA-c598-6h34-q6qw"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MAVLink protocol","requires_auth":"none","summary":"Remote attackers can intercept sensitive data transmitted via the unencrypted MAVLink protocol used in drone autopilots.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Alias","cpe":[{"product":"micro_air_vehicle_link","vendor":"dronecode"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"This vulnerability applies to the Micro Air Vehicle Link (MAVLink) protocol and allows a remote attacker to gain access to sensitive information provided it has access to the communication medium. MAVLink is a header-based protocol that does not perform encryption to improve transfer (and reception speed) and efficiency by design. The increasing popularity of the protocol (used accross different autopilots) has led to its use in wired and wireless mediums through insecure communication channels exposing sensitive information to a remote attacker with ability to intercept network traffic.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"RVD#3315: Cleartext transmission of sensitive information in MAVLink protocol version 1.0 and 2.0","id":"CVE-2020-10281","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"RVD#3316: No authentication in MAVLink protocol","id":"CVE-2020-10282"},"packages":[],"prev":{"headline":"RVD#2568: Apache server is vulnerable to a DoS","id":"CVE-2020-10280"},"products":["MAVLink"],"published":"2020-07-03","related":[{"cvss_score":9.8,"headline":"RVD#3316: No authentication in MAVLink protocol","id":"CVE-2020-10282","kev_date_added":null,"published":"2020-07-03"},{"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"}],"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":"Remote attackers can intercept sensitive data transmitted via the unencrypted MAVLink protocol used in drone autopilots.","url":"https://insights.sbomify.com/CVE-2020-10281/"}