Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2014-0496

Adobe Reader and Acrobat Use-After-Free Vulnerability

Adobe Reader and Acrobat

Use-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.9 and 11.x before 11.0.06 on Windows and Mac OS X allows attackers to execute arbitrary code via unspecified vectors.

CVSS
8.8
HIGH
EPSS
40%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
15 Jan 2014
CWE-416

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 3 March 2022. US federal agencies were required to remediate it by 24 March 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 40%, which is higher than 98.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2014-0496 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2014-0496.

What does CVE-2014-0496 affect?

CVE-2014-0496 affects Adobe Reader and Acrobat. Use-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.9 and 11.x before 11.0.06 on Windows and Mac OS X allows attackers to execute arbitrary code via unspecified vectors.

How severe is CVE-2014-0496?

CVE-2014-0496 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 40%, higher than 98.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 24 March 2022.

How should organisations respond to CVE-2014-0496?

Apply the vendor patch for Adobe Reader and Acrobat as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.