Code execution via crafted-file heap overflow
Published Jan 14, 2022 · Updated Sep 16, 2024
Heap-based buffer overflow in Adobe Acrobat Reader allows attackers to execute code as the current user through a crafted PDF file. Adobe identifies insecure crafted-file handling but does not disclose the parser, data structure, or malformed field responsible for the heap overwrite. Exploitation requires a victim to open the malicious file, after which code runs with that victim's permissions.
Summary
What happened
Heap-based buffer overflow in Adobe Acrobat Reader allows attackers to execute code as the current user through a crafted PDF file. Adobe identifies insecure crafted-file handling but does not disclose the parser, data structure, or malformed field responsible for the heap overwrite. Exploitation requires a victim to open the malicious file, after which code runs with that victim's permissions.
The record
- CVE
- CVE-2021-44709
- Published
- Jan 14, 2022
- Updated
- Sep 16, 2024
- Vendor
- Adobe
- Product
- Adobe Acrobat Reader
- Classifications
- CWE-787, CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=17.011.30204
- Affected versionversion=unspecified <=20.004.30017
- Affected versionversion=unspecified <=21.007.20099
- Affected versionversion=unspecified <=None
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo