CVE-2015-7618: Use After Free
The CBAutoConfigCommentRepository 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-6722, CVE-2015-6723, CVE-2015-6724, CVE-2015-6725, CVE-2015-7614, CVE-2015-7616, 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-7618?
CVE-2015-7618 is considered to have a moderate severity rating due to its potential for JavaScript bypassing in Adobe Reader and Acrobat.
How do I fix CVE-2015-7618?
To fix CVE-2015-7618, update Adobe Acrobat and Acrobat Reader to the latest versions provided by Adobe that address this vulnerability.
What versions of Adobe Acrobat are affected by CVE-2015-7618?
CVE-2015-7618 affects Adobe Acrobat 10.x prior to 10.1.16, 11.x prior to 11.0.13, and certain versions of Acrobat DC.
Can CVE-2015-7618 be exploited remotely?
Yes, CVE-2015-7618 can potentially be exploited remotely through specially crafted PDF files.
Is there a workaround for CVE-2015-7618?
A recommended workaround for CVE-2015-7618 is to disable JavaScript in Adobe Acrobat and Reader until the software has been patched.