CRITICAL · CVSS 9.8 CISA Known Exploited Vulnerability

CVE-2014-0546

Adobe Reader and Acrobat Sandbox Bypass Vulnerability

Adobe Reader and Acrobat

Adobe Reader and Acrobat 10.x before 10.1.11 and 11.x before 11.0.08 on Windows allow attackers to bypass a sandbox protection mechanism, and consequently execute native code in a privileged context, via unspecified vectors.

CVSS
9.8
CRITICAL
EPSS
22.3%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
12 Aug 2014
NVD

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 25 May 2022. US federal agencies were required to remediate it by 15 June 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 22.3%, which is higher than 97.6% 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:N/S:U/C:H/I:H/A:H

Frequently asked questions

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

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

What does CVE-2014-0546 affect?

CVE-2014-0546 affects Adobe Reader and Acrobat. Adobe Reader and Acrobat 10.x before 10.1.11 and 11.x before 11.0.08 on Windows allow attackers to bypass a sandbox protection mechanism, and consequently execute native code in a privileged context, via unspecified vectors.

How severe is CVE-2014-0546?

CVE-2014-0546 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 22.3%, higher than 97.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 June 2022.

How should organisations respond to CVE-2014-0546?

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.