CWE
787
Advisory Published
Updated

CVE-2018-15999

First published: Fri Jan 18 2019(Updated: )

Adobe Acrobat and Reader versions 2019.008.20081 and earlier, 2019.008.20080 and earlier, 2019.008.20081 and earlier, 2017.011.30106 and earlier version, 2017.011.30105 and earlier version, 2015.006.30457 and earlier, and 2015.006.30456 and earlier have an out-of-bounds write vulnerability. Successful exploitation could lead to arbitrary code execution.

Credit: psirt@adobe.com

Affected SoftwareAffected VersionHow to fix
Adobe Acrobat Reader DC>=15.006.30060<=15.006.30457
Adobe Acrobat Reader DC>=15.008.20082<=19.008.20081
Adobe Acrobat Reader DC>=17.011.30056<=17.011.30106
Adobe Acrobat Reader>=15.006.30060<=15.006.30457
Adobe Acrobat Reader>=15.008.20082<=19.008.20081
Adobe Acrobat Reader>=17.011.30059<=17.011.30106
Microsoft Windows Operating System
Adobe Acrobat Reader DC>=15.006.30060<=15.006.30456
Adobe Acrobat Reader DC>=15.008.20082<=19.008.20080
Adobe Acrobat Reader DC>=17.011.30056<=17.011.30105
Adobe Acrobat Reader>=15.006.30060<=15.006.30456
Adobe Acrobat Reader>=15.008.20082<=19.008.20080
Adobe Acrobat Reader>=17.011.30059<=17.011.30105
Apple iOS and macOS

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.

Frequently Asked Questions

  • What is the severity of CVE-2018-15999?

    CVE-2018-15999 has been assigned a high severity level due to its potential for exploitation leading to arbitrary code execution.

  • Which versions of Adobe Acrobat and Reader are affected by CVE-2018-15999?

    CVE-2018-15999 affects Adobe Acrobat and Reader versions 2015.006.30456 and earlier, 2017.011.30105 and earlier, and 2019.008.20080 and earlier.

  • How do I fix CVE-2018-15999?

    To fix CVE-2018-15999, update Adobe Acrobat and Reader to the latest version available from Adobe.

  • What are the potential impacts of exploiting CVE-2018-15999?

    Exploitation of CVE-2018-15999 could allow an attacker to execute arbitrary code on the affected system.

  • Is there a workaround for CVE-2018-15999 if I cannot update immediately?

    There are no specific workarounds for CVE-2018-15999, so updating to the latest version is the recommended action.

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