7.8

CVE-2023-21608

Warning

Adobe Acrobat Reader versions 22.003.20282 (and earlier), 22.003.20281 (and earlier) and 20.005.30418 (and earlier) are affected by a Use After Free vulnerability that could result in 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 <= 22.003.20282
   Microsoft ≫ Windows Version-
Adobe ≫ Acrobat Reader Dc SwEditioncontinuous Version >= 15.008.20082 <= 22.003.20282
   Microsoft ≫ Windows Version-
Adobe ≫ Acrobat Dc SwEditioncontinuous Version >= 15.008.20082 <= 22.003.20281
   Apple ≫ macOS Version-
Adobe ≫ Acrobat Reader Dc SwEditioncontinuous Version >= 15.008.20082 <= 22.003.20281
   Apple ≫ macOS Version-
Adobe ≫ Acrobat SwEditionclassic Version >= 20.001.30005 <= 20.005.30418
   Apple ≫ macOS Version-
   Microsoft ≫ Windows Version-
Adobe ≫ Acrobat Reader SwEditionclassic Version >= 20.001.30005 <= 20.005.30418
   Apple ≫ macOS Version-
   Microsoft ≫ Windows Version-

10.10.2023: CISA Known Exploited Vulnerabilities (KEV) Catalog

Adobe Acrobat and Reader Use-After-Free Vulnerability

Vulnerability

Adobe Acrobat and Reader contains a use-after-free vulnerability that allows for code execution in the context of the current user.

Description

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Required actions
EPSS Metriken
Type Source Score Percentile
EPSS FIRST.org 88.96% 0.995
CVSS Metriken
Source Base Score Exploit Score Impact Score Vector string
psirt@adobe.com 7.8 1.8 5.9
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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.