{"answers":{"affected":"It affects 18 products.","exploited":"There is no known exploitation of CVE-2020-26144 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-26144 is a medium-severity vulnerability in n/a, published on 11 May 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-26144 and fix it if it is affected.\n\nWhat it is: CVE-2020-26144 is a medium-severity vulnerability in n/a, published on 11 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-26144 in the wild and no public exploit code.\n\nAffected product: n/a. 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-26144/ (Markdown: https://insights.sbomify.com/CVE-2020-26144/index.md)","id":"CVE-2020-26144","markdown":"https://insights.sbomify.com/CVE-2020-26144/index.md","name":"CVE-2020-26144","record":{"aliases":["GHSA-89fj-xvf5-gc78","UBUNTU-CVE-2020-26144"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Galaxy S3","requires_auth":"none","summary":"Attackers can inject arbitrary network packets on Samsung Galaxy S3 devices by exploiting a flaw in Wi-Fi frame processing, bypassing network security controls.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"c-100_firmware","vendor":"arista"},{"product":"c-110_firmware","vendor":"arista"},{"product":"c-120_firmware","vendor":"arista"},{"product":"c-130_firmware","vendor":"arista"},{"product":"c-200_firmware","vendor":"arista"},{"product":"c-230_firmware","vendor":"arista"},{"product":"c-235_firmware","vendor":"arista"},{"product":"c-250_firmware","vendor":"arista"},{"product":"c-260_firmware","vendor":"arista"},{"product":"c-65_firmware","vendor":"arista"},{"product":"c-75_firmware","vendor":"arista"},{"product":"o-105_firmware","vendor":"arista"},{"product":"o-90_firmware","vendor":"arista"},{"product":"w-118_firmware","vendor":"arista"},{"product":"w-68_firmware","vendor":"arista"},{"product":"galaxy_i9305_firmware","vendor":"samsung"},{"product":"scalance_w700_ieee_802.11ax_firmware","vendor":"siemens"},{"product":"scalance_w700_ieee_802.11n_firmware","vendor":"siemens"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered on Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept plaintext A-MSDU frames as long as the first 8 bytes correspond to a valid RFC1042 (i.e., LLC/SNAP) header for EAPOL. An adversary can abuse this to inject arbitrary network packets independent of the network configuration.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Other in n/a","id":"CVE-2020-26144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2020"},"n_packages":0,"n_references":6,"next":{"headline":"Other in n/a","id":"CVE-2020-26145"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2020-26143"},"products":["n/a"],"published":"2021-05-11","related":[{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26139","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-26146","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":3.5,"headline":"The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that the","id":"CVE-2020-24588","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":2.6,"headline":"The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that all","id":"CVE-2020-24587","kev_date_added":null,"published":"2021-05-11"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["n/a"]},"summary":"Attackers can inject arbitrary network packets on Samsung Galaxy S3 devices by exploiting a flaw in Wi-Fi frame processing, bypassing network security controls.","url":"https://insights.sbomify.com/CVE-2020-26144/"}