Current-user code execution via heap buffer overflow
Published Sep 2, 2021 · Updated Sep 16, 2024
Heap-based buffer overflow in Adobe Acrobat Reader allows remote attackers to execute code via a malicious file opened by the victim. Adobe has not disclosed the affected parser, input field, or the memory operation that overruns a heap allocation. Exploitation requires the victim to open the crafted file, after which attacker-controlled code runs with the victim's current-user privileges.
Summary
What happened
Heap-based buffer overflow in Adobe Acrobat Reader allows remote attackers to execute code via a malicious file opened by the victim. Adobe has not disclosed the affected parser, input field, or the memory operation that overruns a heap allocation. Exploitation requires the victim to open the crafted file, after which attacker-controlled code runs with the victim's current-user privileges.
The record
- CVE
- CVE-2021-28560
- Published
- Sep 2, 2021
- Updated
- Sep 16, 2024
- Vendor
- Adobe
- Product
- Adobe Acrobat Reader
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2021CVE 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 <=2017.011.30194
- Affected versionversion=unspecified <=2020.001.30020
- Affected versionversion=unspecified <=2021.001.20150
- 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