{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-39701 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2021-39701 is a high-severity vulnerability in Google Android, published on 16 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-39701 and fix it if it is affected.\n\nWhat it is: CVE-2021-39701 is a high-severity vulnerability in Google Android, published on 16 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-39701 in the wild and no public exploit code.\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-2021-39701/ (Markdown: https://insights.sbomify.com/CVE-2021-39701/index.md)","id":"CVE-2021-39701","markdown":"https://insights.sbomify.com/CVE-2021-39701/index.md","name":"CVE-2021-39701","record":{"aliases":["A-212286849","ASB-A-212286849","GHSA-hphp-mxj8-3r85"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android OS","requires_auth":"none","summary":"Local attackers can escalate privileges by keeping a service running in the foreground without notification or permission due to improper input validation.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"google_android","cpe":[{"product":"android","vendor":"google"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"In serviceConnection of ControlsProviderLifecycleManager.kt, there is a possible way to keep service running in foreground without notification or permission due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-11 Android-12Android ID: A-212286849","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":"Privilege escalation in Android","id":"CVE-2021-39701","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"privilege_escalation","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Android","id":"CVE-2021-39702"},"packages":[],"prev":{"headline":"Information disclosure in Android","id":"CVE-2021-39700"},"products":["Android"],"published":"2022-03-16","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Local attackers can escalate privileges by keeping a service running in the foreground without notification or permission due to improper input validation.","url":"https://insights.sbomify.com/CVE-2021-39701/"}