CVE-2013-4787 (Master Key) google android: Cryptographic Issues
Known as Master Key
google android: no CVSS score yet. EPSS 14% estimated probability of exploitation activity in the next 30 days.
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows attackers to execute arbitrary code via an application package file (APK) that is modified in a way that does not violate the cryptographic signature, probably involving multiple entries in a Zip file with the same name in which one entry is validated but the other entry is installed, aka Android security bug 8219321 and the "Master Key" vulnerability.
- EPSS
- 14% (unchanged from 14% a week ago; 14% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-310 Cryptographic Issues
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2013-4787 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2013-4787?via=ask-ai-copy and https://cve.bz/cve/CVE-2013-4787?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2013-4787 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| google:android | 1.6 |
| google:android | 2.0 |
| google:android | 2.0.1 |
| google:android | 2.1 |
| google:android | 2.2 |
| google:android | 2.2:rev1 |
| google:android | 2.2.1 |
| google:android | 2.2.2 |
| google:android | 2.2.3 |
| google:android | 2.3 |
| google:android | 2.3:rev1 |
| google:android | 2.3.1 |
| google:android | 2.3.2 |
| google:android | 2.3.3 |
| google:android | 2.3.4 |
| google:android | 2.3.5 |
| google:android | 2.3.6 |
| google:android | 2.3.7 |
| google:android | 3.0 |
| google:android | 3.1 |
| google:android | 3.2 |
| google:android | 3.2.1 |
| google:android | 3.2.2 |
| google:android | 3.2.4 |
| google:android | 3.2.6 |
| google:android | 4.0 |
| google:android | 4.0.1 |
| google:android | 4.0.2 |
| google:android | 4.0.3 |
| google:android | 4.0.4 |
| google:android | 4.1 |
| google:android | 4.1.2 |
| google:android | 4.2 |
Public exploits
References
- http://bluebox.com/corporate-blog/bluebox-uncovers-android-master-key/
- http://review.cyanogenmod.org/#/c/45251/
- http://www.osvdb.org/94773
- http://www.securityfocus.com/bid/60952
- http://www.zdnet.com/google-releases-fix-to-oems-for-blue-security-android-security-hole-7000017782/
- https://jira.cyanogenmod.org/browse/CYAN-1602
- https://plus.google.com/113331808607528811927/posts/GxDA6111vYy