{"answers":{"affected":"It affects 29 products.","exploited":"Yes. Attackers have exploited CVE-2020-0069 in the wild since at least 3 Nov 2021.","fix":"No fix has been published for CVE-2020-0069 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.","what":"CVE-2020-0069 is a high-severity memory corruption vulnerability in Google Android, published on 10 Mar 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-0069 and fix it if it is affected.\n\nWhat it is: CVE-2020-0069 is a high-severity memory corruption vulnerability in Google Android, published on 10 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2020-0069 in the wild since at least 3 Nov 2021.\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-0069/ (Markdown: https://insights.sbomify.com/CVE-2020-0069/index.md)","id":"CVE-2020-0069","markdown":"https://insights.sbomify.com/CVE-2020-0069/index.md","name":"CVE-2020-0069","record":{"aliases":["GHSA-xx48-fp29-wh9j"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android kernel","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges via an out-of-bounds write in the Mediatek Command Queue driver due to insufficient input sanitization.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"google_android","cpe":[{"product":"android","vendor":"google"},{"product":"berkeley-l09_firmware","vendor":"huawei"},{"product":"columbia-al10b_firmware","vendor":"huawei"},{"product":"columbia-l29d_firmware","vendor":"huawei"},{"product":"columbia-tl00b_firmware","vendor":"huawei"},{"product":"columbia-tl00d_firmware","vendor":"huawei"},{"product":"cornell-al00a_firmware","vendor":"huawei"},{"product":"cornell-tl10b_firmware","vendor":"huawei"},{"product":"dura-al00a_firmware","vendor":"huawei"},{"product":"honor_20_pro_firmware","vendor":"huawei"},{"product":"honor_8a_firmware","vendor":"huawei"},{"product":"honor_view_20_firmware","vendor":"huawei"},{"product":"jakarta-al00a_firmware","vendor":"huawei"},{"product":"katyusha-al00a_firmware","vendor":"huawei"},{"product":"katyusha-al10a_firmware","vendor":"huawei"},{"product":"madrid-al00a_firmware","vendor":"huawei"},{"product":"nova_3_firmware","vendor":"huawei"},{"product":"nova_4_firmware","vendor":"huawei"},{"product":"paris-l29b_firmware","vendor":"huawei"},{"product":"princeton-al10b_firmware","vendor":"huawei"},{"product":"sydney-al00_firmware","vendor":"huawei"},{"product":"sydney-tl00_firmware","vendor":"huawei"},{"product":"sydneym-al00_firmware","vendor":"huawei"},{"product":"tony-al00b_firmware","vendor":"huawei"},{"product":"tony-tl00b_firmware","vendor":"huawei"},{"product":"y6_2019_firmware","vendor":"huawei"},{"product":"yale-al00a_firmware","vendor":"huawei"},{"product":"yale-l21a_firmware","vendor":"huawei"},{"product":"yalep-al10b_firmware","vendor":"huawei"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In the ioctl handlers of the Mediatek Command Queue driver, there is a possible out of bounds write due to insufficient input sanitization and missing SELinux restrictions. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-147882143References: M-ALPS04356754","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2019-09-06","github_poc":4,"max_poc_stars":188,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-09-06T12:12:48Z","kind":"github_poc","ref":"https://github.com/R0rt1z2/AutomatedRoot","stars":188,"title":"Root your MediaTek device with CVE-2020-0069"},{"date":"2020-03-24T13:10:39Z","kind":"github_poc","ref":"https://github.com/quarkslab/CVE-2020-0069_poc","stars":111,"title":null},{"date":"2020-03-03T22:55:42Z","kind":"github_poc","ref":"https://github.com/TheRealJunior/mtk-su-reverse-cve-2020-0069","stars":17,"title":"reversing mtk-su"},{"date":"2023-09-04T17:52:04Z","kind":"github_poc","ref":"https://github.com/0xf15h/mtk_su","stars":14,"title":"CVE-2020-0069"}],"tier":"exploited"},"has_fix":null,"headline":"Mediatek Multiple Chipsets Insufficient Input Validation","id":"CVE-2020-0069","indexable":true,"kev":{"dateAdded":"2021-11-03","dueDate":"2022-05-03","knownRansomwareCampaignUse":"Unknown","product":"Multiple Chipsets","requiredAction":"Apply updates per vendor instructions.","vendorProject":"MediaTek","vulnerabilityName":"Mediatek Multiple Chipsets Insufficient Input Validation Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Android","id":"CVE-2020-0070"},"packages":[],"prev":{"headline":"Integer overflow in Android","id":"CVE-2020-0068"},"products":["Android"],"published":"2020-03-10","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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"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":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["n/a"]},"summary":"Local attackers can escalate privileges via an out-of-bounds write in the Mediatek Command Queue driver due to insufficient input sanitization.","url":"https://insights.sbomify.com/CVE-2020-0069/"}