Skip to content
Fencer Intel
critical 9.3

CVE-2014-0514 in the critical feed json

The Adobe Reader Mobile application before 11.2 for Android does not properly restrict use of JavaScript, which allows remote attackers to…

published 12y ago modified 4mo ago also EUVD-2014-0545

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
72.1%
EPSS 72.1% chance of exploitation in 30 days, percentile 99.4%
public exploits
3
Metasploit and Exploit-DB

Summary

The Adobe Reader Mobile application before 11.2 for Android does not properly restrict use of JavaScript, which allows remote attackers to execute arbitrary code via a crafted PDF document, a related issue to CVE-2012-6636.

Patch / fix

Is CVE-2014-0514 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

  1. First public exploit (Metasploit exploit/android/fileformat/adobe_reader_pdf_js_interface)
  2. Published

Exploit prediction

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

Exploits and checks

  • Metasploit exploit/android/fileformat/adobe_reader_pdf_js_interface Adobe Reader for Android addJavascriptInterface Exploit metasploit exploit, good rank, 2014-04-13
  • EDB-33791 Adobe Reader for Android < 11.2.0 - 'addJavascriptInterface' Local Overflow (Metasploit) local, 2014-06-17
  • EDB-32884 Adobe Reader for Android 11.1.3 - Arbitrary JavaScript Execution local, 2014-04-15
  • seclists.org http://seclists.org/fulldisclosure/2014/Apr/192 referenced PoC, tagged "exploit" by a source, unverified
  • securify.nl http://www.securify.nl/advisory/SFY20140401/adobe_reader_for_android_exposes_insecure_javascript_interfaces.html referenced PoC, tagged "exploit" by a source, unverified

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-264 Permissions, Privileges, and Access Controls

References

Sources

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.