CVE-2022-24101: Adobe Acrobat Reader DC Annotation Use-After-Free Information Disclosure Vulnerability
Acrobat Reader DC versions 20.001.20085 (and earlier), 20.005.3031x (and earlier) and 17.012.30205 (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.
Security readout for executives and security teams
Plain-English summary
This is a low-severity Adobe Acrobat Reader memory-disclosure flaw. A victim must open a malicious PDF-like file locally. The main business risk is not direct takeover, but leaking memory that could help bypass protections such as ASLR in a broader attack chain.
Executive priority
Treat as routine endpoint patching unless your organization has heavy exposure to external documents. The weakness can assist exploit chains, but the provided evidence supports low standalone severity and no confirmed active exploitation.
Technical view
CVE-2022-24101 is a CWE-416 use-after-free in Adobe Acrobat Reader DC annotation handling. Affected versions include 20.001.20085 and earlier, 20.005.3031x and earlier, and 17.012.30205 and earlier. CVSS 3.0 is 3.3: local attack vector, no privileges, user interaction required, low confidentiality impact.
Likely exposure
Exposure is limited to systems running the affected Adobe Acrobat Reader versions where users may open untrusted files. It is endpoint-focused, not a server-side remote service issue based on the provided sources.
Exploitation context
The provided sources say exploitation requires user interaction: the victim must open a malicious file. CISA KEV status is false in the bundle, and no cited source here confirms active exploitation.
Researcher notes
The key security value is possible sensitive memory disclosure and mitigation bypass assistance, not integrity or availability impact. Evidence in the bundle does not provide proof-of-concept details, exploit status, or exact fixed build numbers.
Mitigation direction
Review Adobe APSB22-16 for vendor update guidance.
Update affected Adobe Acrobat Reader installations per Adobe guidance.
Reduce user exposure to untrusted PDF files and attachments.
Prioritize users handling external documents or high-risk email flows.
Validation and detection
Inventory Acrobat Reader versions across managed endpoints.
Flag versions at or below the affected release lines.
Confirm remediation against Adobe APSB22-16 guidance.
Review endpoint telemetry for suspicious document-opening activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.