CWE
416
Advisory Published
Updated

CVE-2022-28250: Adobe Acrobat Reader DC Annotation Use-After-Free Information Disclosure Vulnerability

First published: Wed May 11 2022(Updated: )

Acrobat Reader DC version 22.001.2011x (and earlier), 20.005.3033x (and earlier) and 17.012.3022x (and earlier) are affected by a use-after-free vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Credit: psirt@adobe.com

Affected SoftwareAffected VersionHow to fix
Adobe Acrobat Reader DC>=15.008.20082<=22.001.20085
Adobe Acrobat Reader>=15.008.20082<=22.001.20085
macOS
Microsoft Windows Operating System
Adobe Acrobat Reader>=17.011.30059<=17.012.30205
Adobe Acrobat Reader Notification Manager>=17.011.30059<=17.012.30205
Adobe Acrobat Reader>=20.001.30005<=20.005.30314
Adobe Acrobat Reader Notification Manager>=20.001.30005<=20.005.30314
Adobe Acrobat Reader>=20.001.30005<=20.005.30311
Adobe Acrobat Reader Notification Manager>=20.001.30005<=20.005.30311

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-2022-28250?

    CVE-2022-28250 is classified as a critical vulnerability due to its potential to disclose sensitive memory information.

  • How do I fix CVE-2022-28250?

    To remediate CVE-2022-28250, users should update Adobe Acrobat Reader DC to version 22.001.2011 or later, or the corresponding versions for other affected products.

  • Which versions of Adobe Acrobat are affected by CVE-2022-28250?

    CVE-2022-28250 affects Adobe Acrobat Reader DC versions 22.001.2011 and earlier, 20.005.3033 and earlier, and 17.012.3022 and earlier.

  • Can CVE-2022-28250 allow an attacker to execute arbitrary code?

    CVE-2022-28250 primarily allows for sensitive memory disclosure rather than direct arbitrary code execution.

  • Is there a workaround for CVE-2022-28250?

    There are no known workarounds for CVE-2022-28250 other than applying the necessary updates to the affected software.

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