Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows attackers to execu…

published 2013-07-09 13y ago modified 2026-06-16 4mo ago also EUVD-2013-4633

cvss: 9.3; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 13.5%; EPSS 13.5% chance of exploitation in 30 days, percentile 96%
public exploits: 1; Exploit-DB

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.

Is CVE-2013-4787 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

2013-07-03 First public exploit (EDB-38627)
2013-07-09 Published

Exploit prediction

13.53% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

EDB-38627 Google Android - 'APK' code Remote Security Bypass remote, 2013-07-03

CVSS scores

assigned by	version	score	vector
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-310 Cryptographic Issues

References

Sources

CVE List CVE-2013-4787
NVD CVE-2013-4787

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.