First published: Thu Oct 13 2016(Updated: )
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-7018, and CVE-2016-7019.
Credit: psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
Apple iOS and macOS | ||
Microsoft Windows Operating System | ||
Adobe Acrobat Reader | <=11.0.17 | |
Adobe Acrobat Reader DC | <=15.006.30201 | |
Adobe Acrobat Reader DC | <=15.017.20053 | |
Adobe Acrobat Reader | <=15.006.30201 | |
Adobe Acrobat Reader | <=15.017.20053 | |
Adobe Acrobat Reader | <=11.0.17 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-7017 is considered critical due to its potential to allow arbitrary code execution.
To remediate CVE-2016-7017, update Adobe Reader and Acrobat to the latest versions provided by Adobe.
Affected versions include Adobe Reader and Acrobat versions before 11.0.18, Acrobat Reader DC Classic before 15.006.30243, and Continuous version before 15.020.20039.
CVE-2016-7017 can facilitate arbitrary code execution and result in memory corruption leading to denial of service.
There are no specific workarounds listed for CVE-2016-7017; updating the software is the recommended action.