CVE-2017-16360: Use After Free
First published: Sat Dec 09 2017(Updated: )
An issue was discovered in Adobe Acrobat and Reader: 2017.012.20098 and earlier versions, 2017.011.30066 and earlier versions, 2015.006.30355 and earlier versions, and 11.0.22 and earlier versions. This vulnerability is an instance of a use after free vulnerability in the MakeAccessible plugin, when creating an internal data structure. The mismatch between an old and a new object can provide an attacker with unintended memory access -- potentially leading to code corruption, control-flow hijack, or an information leak attack. Successful exploitation could lead to arbitrary code execution.
Credit: psirt@adobe.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Adobe Acrobat Reader | <=11.0.22 | |
| Adobe Acrobat Reader | >=17.0<=17.011.30066 | |
| Adobe Acrobat Reader DC | >=-<=17.012.20098 | |
| Adobe Acrobat Reader DC | >=15.0<=15.006.30355 | |
| Adobe Acrobat Reader Notification Manager | <=11.0.22 | |
| Adobe Acrobat Reader Notification Manager | >=17.0<=17.011.30066 | |
| Adobe Acrobat Reader | >=-<=17.012.20098 | |
| Adobe Acrobat Reader | >=15.0<=15.006.30355 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-16360?
CVE-2017-16360 has been rated as critical due to its potential to allow an attacker to execute arbitrary code.
How do I fix CVE-2017-16360?
To mitigate CVE-2017-16360, update Adobe Acrobat and Reader to the latest version available.
What versions of Adobe products are affected by CVE-2017-16360?
CVE-2017-16360 affects Adobe Acrobat versions prior to 11.0.22 and certain versions of Acrobat DC and Reader before specified updates.
What is a use-after-free vulnerability in the context of CVE-2017-16360?
A use-after-free vulnerability like CVE-2017-16360 allows attackers to manipulate memory after it has been freed, potentially leading to code execution.
Is there a workaround for CVE-2017-16360 before applying a patch?
Currently, the recommended approach for CVE-2017-16360 is to apply the latest software updates rather than relying on workarounds.
- agent/type
- agent/severity
- agent/weakness
- agent/references
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/adobe
- canonical/adobe acrobat reader
- version/adobe acrobat reader/11.0.22
- version/adobe acrobat reader/17.0
- version/adobe acrobat reader/17.011.30066
- canonical/adobe acrobat reader dc
- version/adobe acrobat reader dc/-
- version/adobe acrobat reader dc/17.012.20098
- version/adobe acrobat reader dc/15.0
- version/adobe acrobat reader dc/15.006.30355
- canonical/adobe acrobat reader notification manager
- version/adobe acrobat reader notification manager/11.0.22
- version/adobe acrobat reader notification manager/17.0
- version/adobe acrobat reader notification manager/17.011.30066
- version/adobe acrobat reader/-
- version/adobe acrobat reader/17.012.20098
- version/adobe acrobat reader/15.0
- version/adobe acrobat reader/15.006.30355