{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6271 exists.","fix":"No fix has been published for CVE-2013-6271 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-6271 is a high-severity authentication bypass vulnerability in Google Android, published on 14 Dec 2013. 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-2013-6271 and fix it if it is affected.\n\nWhat it is: CVE-2013-6271 is a high-severity authentication bypass vulnerability in Google Android, published on 14 Dec 2013. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6271 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-2013-6271/ (Markdown: https://insights.sbomify.com/CVE-2013-6271/index.md)","id":"CVE-2013-6271","markdown":"https://insights.sbomify.com/CVE-2013-6271/index.md","name":"CVE-2013-6271","record":{"aliases":["GHSA-7jx4-gmg6-rjv2"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android OS","requires_auth":"low_privilege","summary":"A malicious app can bypass Android device lock restrictions by invoking a specific settings method, allowing unauthorized access to the device.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"android","vendor":"google"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Android 4.0 through 4.3 allows attackers to bypass intended access restrictions and remove device locks via a crafted application that invokes the updateUnlockMethodAndFinish method in the com.android.settings.ChooseLockGeneric class with the PASSWORD_QUALITY_UNSPECIFIED option.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2013-10-11","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2013-10-11","kind":"metasploit","ref":"post/android/manage/remove_lock","stars":null,"title":"Android Settings Remove Device Locks (4.0-4.3)"}],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2013-6271","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"auth_bypass","year":"2013"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in n/a","id":"CVE-2013-6272"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-6267"},"products":["n/a"],"published":"2013-12-14","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":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"A malicious app can bypass Android device lock restrictions by invoking a specific settings method, allowing unauthorized access to the device.","url":"https://insights.sbomify.com/CVE-2013-6271/"}