CVE-2015-6722: Medium severity adobe acrobat reader vulnerability
The CBSharedReviewStatusDialog method in Adobe Reader and Acrobat 10.x before 10.1.16 and 11.x before 11.0.13, Acrobat and Acrobat Reader DC Classic before 2015.006.30094, and Acrobat and Acrobat Reader DC Continuous before 2015.009.20069 on Windows and OS X allows attackers to bypass JavaScript API execution restrictions via unspecified vectors, a different vulnerability than CVE-2015-6707, CVE-2015-6708, CVE-2015-6709, CVE-2015-6710, CVE-2015-6711, CVE-2015-6712, CVE-2015-6713, CVE-2015-6714, CVE-2015-6715, CVE-2015-6716, CVE-2015-6717, CVE-2015-6718, CVE-2015-6719, CVE-2015-6720, CVE-2015-6721, CVE-2015-6723, CVE-2015-6724, CVE-2015-6725, CVE-2015-7614, CVE-2015-7616, CVE-2015-7618, CVE-2015-7619, CVE-2015-7620, and CVE-2015-7623.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2015-6722?
CVE-2015-6722 has been classified as a critical vulnerability due to its potential to allow unauthorized access to sensitive features.
How do I fix CVE-2015-6722?
To fix CVE-2015-6722, users should update Adobe Reader and Acrobat to the latest versions provided by Adobe.
What software versions are affected by CVE-2015-6722?
CVE-2015-6722 affects Adobe Reader and Acrobat versions prior to 10.1.16 for 10.x, 11.0.13 for 11.x, and certain versions of Acrobat Reader DC.
What kind of attacks does CVE-2015-6722 enable?
CVE-2015-6722 enables attackers to bypass the JavaScript API, potentially leading to unauthorized access and manipulation of documents.
Is there a workaround for CVE-2015-6722?
While the recommended solution is to update the software, temporarily restricting the use of JavaScript in Adobe products may mitigate some risks associated with CVE-2015-6722.