CVE-2016-7018: Buffer Overflow
Adobe Reader and Acrobat before 11.0.18, Acrobat and Acrobat Reader DC Classic before 15.006.30243, and Acrobat and Acrobat Reader DC Continuous before 15.020.20039 on Windows and OS X allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2016-6940, CVE-2016-6941, CVE-2016-6942, CVE-2016-6943, CVE-2016-6947, CVE-2016-6948, CVE-2016-6950, CVE-2016-6951, CVE-2016-6954, CVE-2016-6955, CVE-2016-6956, CVE-2016-6959, CVE-2016-6960, CVE-2016-6966, CVE-2016-6970, CVE-2016-6972, CVE-2016-6973, CVE-2016-6974, CVE-2016-6975, CVE-2016-6976, CVE-2016-6977, CVE-2016-6978, CVE-2016-6995, CVE-2016-6996, CVE-2016-6997, CVE-2016-6998, CVE-2016-7000, CVE-2016-7001, CVE-2016-7002, CVE-2016-7003, CVE-2016-7004, CVE-2016-7005, CVE-2016-7006, CVE-2016-7007, CVE-2016-7008, CVE-2016-7009, CVE-2016-7010, CVE-2016-7011, CVE-2016-7012, CVE-2016-7013, CVE-2016-7014, CVE-2016-7015, CVE-2016-7016, CVE-2016-7017, and CVE-2016-7019.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2016-7018?
CVE-2016-7018 is considered critical due to its potential for arbitrary code execution and denial of service.
How do I fix CVE-2016-7018?
To fix CVE-2016-7018, update Adobe Reader and Acrobat to version 11.0.18 or later, or the specified versions of Acrobat DC.
What software is affected by CVE-2016-7018?
CVE-2016-7018 affects Adobe Reader and Acrobat before versions 11.0.18, 15.006.30243, and 15.020.20039.
Can CVE-2016-7018 lead to data loss?
Yes, CVE-2016-7018 can potentially result in data loss due to memory corruption and unauthorized access.
Is there a workaround for CVE-2016-7018?
There are no known workarounds for CVE-2016-7018; updating the software is the recommended action.