Vulnerability in Google Android
CVE-2013-4787
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.
Published · last modified .
CVSS v2 metric
CVSS v2 base score 9.3 (High). Vector: AV:N/AC:M/Au:N/C:C/I:C/A:C. This CVE predates CVSS v3 and has no v3 score from NVD.
EPSS exploit prediction
EPSS 0.135, 96.5th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Google Android — versions 1.6, 2.0, 2.0.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (ARPSyndicate/cve-scores). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- www.securityfocus.com/bid/60952 (vdb-entry)
- jira.cyanogenmod.org/browse/CYAN-1602
- plus.google.com/113331808607528811927/posts/GxDA6111vYy
- www.zdnet.com/google-releases-fix-to-oems-for-blue-security-android-security-ho…
- bluebox.com/corporate-blog/bluebox-uncovers-android-master-key/
- www.osvdb.org/94773 (vdb-entry)
- review.cyanogenmod.org/