9.6
CVE-2021-28550
- EPSS 22.45%
- Published 02.09.2021 17:15:08
- Last modified 13.02.2025 17:30:34
- Source psirt@adobe.com
- Teams watchlist Login
- Open Login
Acrobat Reader DC versions versions 2021.001.20150 (and earlier), 2020.001.30020 (and earlier) and 2017.011.30194 (and earlier) are affected by a Use After Free vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Data is provided by the National Vulnerability Database (NVD)
Adobe ≫ Acrobat Dc SwEditioncontinuous Version >= 15.008.20082 <= 21.001.20150
Adobe ≫ Acrobat Reader Dc SwEditioncontinuous Version >= 15.008.20082 <= 21.001.20150
Adobe ≫ Acrobat Reader SwEditionclassic Version >= 17.011.30059 <= 17.011.30194
Adobe ≫ Acrobat Reader SwEditionclassic Version >= 20.001.30005 <= 20.001.30020
Adobe ≫ Acrobat Dc SwEditioncontinuous Version >= 15.008.20082 <= 21.001.20150
Adobe ≫ Acrobat Reader Dc SwEditioncontinuous Version >= 15.008.20082 <= 21.001.20150
03.11.2021: CISA Known Exploited Vulnerabilities (KEV) Catalog
Adobe Acrobat and Reader Use-After-Free Vulnerability
VulnerabilityAdobe Acrobat and Reader contains a use-after-free vulnerability that could allow an unauthenticated attacker to achieve code execution in the context of the current user.
DescriptionApply updates per vendor instructions.
Required actions| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 22.45% | 0.956 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 8.8 | 2.8 | 5.9 |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
|
| nvd@nist.gov | 6.8 | 8.6 | 6.4 |
AV:N/AC:M/Au:N/C:P/I:P/A:P
|
| psirt@adobe.com | 9.6 | 2.8 | 6 |
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.