{"answers":{"affected":"It affects 22 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-0022 exists.","fix":"No fix has been published for CVE-2020-0022 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-0022 is a high-severity memory corruption vulnerability in Google Android, published on 13 Feb 2020. 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-0022 and fix it if it is affected.\n\nWhat it is: CVE-2020-0022 is a high-severity memory corruption vulnerability in Google Android, published on 13 Feb 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-0022 exists.\n\nAffected product: Google Android. 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-0022/ (Markdown: https://insights.sbomify.com/CVE-2020-0022/index.md)","id":"CVE-2020-0022","markdown":"https://insights.sbomify.com/CVE-2020-0022/index.md","name":"CVE-2020-0022","record":{"aliases":["GHSA-55v6-vvqw-j3qq"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android OS","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via Bluetooth due to an out-of-bounds write in the packet fragmenter, requiring no user interaction.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"google_android","cpe":[{"product":"android","vendor":"google"},{"product":"honor_8a_firmware","vendor":"huawei"},{"product":"honor_8x_firmware","vendor":"huawei"},{"product":"honor_view_20_firmware","vendor":"huawei"},{"product":"mate_20_firmware","vendor":"huawei"},{"product":"mate_20_pro_firmware","vendor":"huawei"},{"product":"mate_20_x_firmware","vendor":"huawei"},{"product":"mate_30_5g_firmware","vendor":"huawei"},{"product":"mate_30_firmware","vendor":"huawei"},{"product":"mate_30_pro_5g_firmware","vendor":"huawei"},{"product":"mate_30_pro_firmware","vendor":"huawei"},{"product":"nova_3_firmware","vendor":"huawei"},{"product":"nova_lite_3_firmware","vendor":"huawei"},{"product":"p20_firmware","vendor":"huawei"},{"product":"p20_pro_firmware","vendor":"huawei"},{"product":"p30_firmware","vendor":"huawei"},{"product":"p30_pro_firmware","vendor":"huawei"},{"product":"p_smart_2019_firmware","vendor":"huawei"},{"product":"p_smart_firmware","vendor":"huawei"},{"product":"y6_2019_firmware","vendor":"huawei"},{"product":"y6_pro_2019_firmware","vendor":"huawei"},{"product":"y9_2019_firmware","vendor":"huawei"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-682","name":"Incorrect Calculation"}],"description":"In reassemble_and_dispatch of packet_fragmenter.cc, there is possible out of bounds write due to an incorrect bounds calculation. This could lead to remote code execution over Bluetooth with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-143894715","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-02-15","github_poc":9,"max_poc_stars":65,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-02-15T16:55:44Z","kind":"github_poc","ref":"https://github.com/leommxj/cve-2020-0022","stars":65,"title":"poc for cve-2020-0022"},{"date":"2020-08-24T19:33:10Z","kind":"github_poc","ref":"https://github.com/Polo35/CVE-2020-0022","stars":37,"title":"CVE-2020-0022 vulnerability exploitation on Bouygues BBox Miami (Android TV 8.0 - ARM32 Cortex A9)"},{"date":"2020-07-01T00:23:33Z","kind":"github_poc","ref":"https://github.com/k3vinlusec/Bluefrag_CVE-2020-0022","stars":33,"title":"This is a RCE bluetooth vulnerability on Android 8.0 and 9.0"},{"date":"2023-08-28T09:20:38Z","kind":"github_poc","ref":"https://github.com/themmokhtar/CVE-2020-0022","stars":22,"title":"A fully public exploit of the CVE-2020-0022 BlueFrag Android RCE Vulnerability (tested on Pixel 3 XL)"},{"date":"2020-12-16T06:25:41Z","kind":"github_poc","ref":"https://github.com/5k1l/cve-2020-0022","stars":4,"title":"cve-2020-0022相关的一些东西"},{"date":"2021-02-24T13:17:41Z","kind":"github_poc","ref":"https://github.com/lsw29475/CVE-2020-0022","stars":4,"title":null},{"date":"2020-03-09T12:25:49Z","kind":"github_poc","ref":"https://github.com/idkwim/CVE-2020-0022","stars":0,"title":"BlueFrag  experiments"},{"date":"2021-11-03T15:48:53Z","kind":"github_poc","ref":"https://github.com/devdanqtuan/poc-for-cve-2020-0022","stars":0,"title":"cve-2020-0022"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in Android","id":"CVE-2020-0022","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in Android","id":"CVE-2020-0023"},"packages":[],"prev":{"headline":"Denial of service in Android","id":"CVE-2020-0021"},"products":["Android"],"published":"2020-02-13","related":[{"cvss_score":8.8,"headline":"Google Pixel Improper Authorization","id":"CVE-2026-58704","kev_date_added":"2026-09-16","published":"2026-09-15"},{"cvss_score":8.8,"headline":"Android Runtime Use-After-Free","id":"CVE-2025-48543","kev_date_added":"2025-09-04","published":"2025-09-04"},{"cvss_score":8.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2023-35674","kev_date_added":"2023-09-13","published":"2023-09-11"},{"cvss_score":8.4,"headline":"Android Framework Integer Overflow","id":"CVE-2025-48595","kev_date_added":"2026-06-02","published":"2026-06-01"},{"cvss_score":8.1,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-32896","kev_date_added":"2024-06-13","published":"2024-06-13"},{"cvss_score":7.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2025-48572","kev_date_added":"2025-12-02","published":"2025-12-08"},{"cvss_score":7.8,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-29748","kev_date_added":"2024-04-04","published":"2024-04-05"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via Bluetooth due to an out-of-bounds write in the packet fragmenter, requiring no user interaction.","url":"https://insights.sbomify.com/CVE-2020-0022/"}