Loading vulnerability…
A vulnerability in Android versions 4.0 through 4.3 allows a local attacker to bypass device lockscreen protections. By crafting a malicious application that invokes the updateUnlockMethodAndFinish method in the com.android.settings.ChooseLockGeneric class with the PASSWORD_QUALITY_UNSPECIFIED option, an attacker can remove the device lock, circumventing intended access restrictions.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit post-exploitation module written in Ruby, targeting Android devices running versions 4.0 to 4.3. The module exploits CVE-2013-6271, a logic flaw in the com.android.settings.ChooseLockGeneric class, allowing an attacker with a Meterpreter or shell session to remove the device lockscreen. The exploit works by sending a crafted Intent to the vulnerable settings component, effectively clearing the lockscreen and allowing the device to be unlocked with a swipe. The module checks the Android version by reading the build.prop file and only proceeds if the device is within the vulnerable range. The exploit is operational and requires an existing session on the target device. No network endpoints are involved; the attack vector is local, leveraging Android's inter-process communication via Intents.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.