critical
9.3
CWE
704
Advisory Published
Updated

CVE-2017-2962: Incorrect Type Cast

First published: Wed Jan 11 2017(Updated: )

Adobe Acrobat Reader versions 15.020.20042 and earlier, 15.006.30244 and earlier, 11.0.18 and earlier have an exploitable type confusion vulnerability in the XSLT engine related to localization functionality. Successful exploitation could lead to arbitrary code execution.

Credit: psirt@adobe.com

Affected SoftwareAffected VersionHow to fix
Adobe Acrobat Reader<=11.0.18
Adobe Acrobat Reader DC<=15.006.30244
Adobe Acrobat Reader DC<=15.020.20042
Adobe Acrobat Reader<=15.006.30244
Adobe Acrobat Reader<=15.020.20042
Adobe Acrobat Reader<=11.0.18
Apple iOS and macOS
Microsoft Windows Operating System
All of
Any of
Adobe Acrobat Reader<=11.0.18
Adobe Acrobat Reader DC<=15.006.30244
Adobe Acrobat Reader DC<=15.020.20042
Adobe Acrobat Reader<=15.006.30244
Adobe Acrobat Reader<=15.020.20042
Adobe Acrobat Reader<=11.0.18
Any of
Apple iOS and macOS
Microsoft Windows Operating System

Remedy

https://helpx.adobe.com/security/products/acrobat/apsb17-01.html

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2017-2962?

    CVE-2017-2962 is considered a critical vulnerability due to its potential to allow arbitrary code execution.

  • How do I fix CVE-2017-2962?

    To fix CVE-2017-2962, update Adobe Acrobat Reader and Acrobat DC to the latest version as recommended by Adobe.

  • Which versions are affected by CVE-2017-2962?

    CVE-2017-2962 affects Adobe Acrobat Reader versions 11.0.18 and earlier, and Acrobat DC versions 15.006.30244 and earlier, as well as 15.020.20042 and earlier.

  • What kind of attack could exploit CVE-2017-2962?

    Exploitation of CVE-2017-2962 could lead to arbitrary code execution through a type confusion vulnerability in the XSLT engine.

  • Is there any workaround for CVE-2017-2962?

    There are no recommended workarounds for CVE-2017-2962; applying the update is the best mitigation.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203