CVE-2013-4787

Description

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.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
13.527%
chance of exploitation in the next 30 days
higher than 96.5% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0
Exploit-DB: 1

Weakness

Timeline

  1. 2013-07-03First Exploit-DB entry (EDB-ID 38627)6 days before publication
  2. 2013-07-09Published by the CNA17:00 UTC

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

Exploit-DBTypePlatformPublishedEDB-verified
EDB-ID 38627remoteandroid2013-07-03yes

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
google android1.6no fix listed2.0no fix listed2.0.1no fix listed2.1no fix listed2.2no fix listed(+26 more)not listednot listednot listednot listednot listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources