{"id":"CVE-2013-4787","published":"2013-07-09T17:00:00Z","modified":"2024-09-17T03:59:38Z","title":"Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which…","vendor":null,"product":null,"tier":"tail","description":{"text":"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.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.13527,"percentile":0.96539,"provenance":"source"},"cwes":[],"references":[{"url":"http://www.securityfocus.com/bid/60952","tags":["vdb-entry","x_refsource_BID"]},{"url":"https://jira.cyanogenmod.org/browse/CYAN-1602","tags":["x_refsource_MISC"]},{"url":"https://plus.google.com/113331808607528811927/posts/GxDA6111vYy","tags":["x_refsource_MISC"]},{"url":"http://www.zdnet.com/google-releases-fix-to-oems-for-blue-security-android-security-hole-7000017782/","tags":["x_refsource_MISC"]},{"url":"http://bluebox.com/corporate-blog/bluebox-uncovers-android-master-key/","tags":["x_refsource_MISC"]},{"url":"http://www.osvdb.org/94773","tags":["vdb-entry","x_refsource_OSVDB"]},{"url":"http://review.cyanogenmod.org/#/c/45251/","tags":["x_refsource_MISC"]}],"priority":{"score":24.3,"factors":[{"name":"EPSS percentile","points":19.31},{"name":"Public exploit code","points":5.0}]},"exploitSources":{"exploitdb":{"count":1,"earliest":"2013-07-03"},"first":{"date":"2013-07-03","source":"Exploit-DB","url":"https://www.exploit-db.com/exploits/38627"},"provenance":"source"},"summary":{"text":"The flaw is in how Android 1.6 Donut through 4.2 Jelly Bean verifies cryptographic signatures on application packages (APK files), so the signature check does not properly cover the content that is actually installed. An attacker who supplies an APK modified in a way that keeps the signature valid, probably by including multiple Zip entries with the same name where only one is validated, can execute arbitrary code on the device.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T06:49:31Z"},"euvd":{"id":"EUVD-2013-4633","exploited":false,"provenance":"source"},"exploits":[{"id":38627,"url":"https://www.exploit-db.com/exploits/38627","title":"Google Android - 'APK' code Remote Security Bypass","date":"2013-07-03","verified":true,"provenance":"source"}]}