Loading vulnerability…
CVE-2013-4787, known as the Android Master Key vulnerability (Android security bug 8219321), affects Android 1.6 Donut through 4.2 Jelly Bean. The application-package signature verification logic improperly handles APK ZIP archives containing multiple entries with the same name. Android can validate the cryptographic signature of one entry but subsequently install a different same-named entry. This lets an attacker modify an APK's effective installed contents without invalidating the original application signature.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An Android APK signature-validation flaw affecting Android 1.6 through 4.2 that permits arbitrary code execution by modifying an APK without invalidating its cryptographic signature, using duplicate ZIP entries such that a validated entry differs from the installed entry.
A duplicate-file-name archive handling flaw in a mobile OS, where the signature verifier checks one archive member but the installer installs a different member with the same name.
A vulnerability involving archive contents in which a mobile operating system verifies the cryptographic signature of one file but installs a different archive file with the same name.
A vulnerability involving verification of a cryptographically signed archive file followed by installation of a different archive file sharing the same name.
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.