Current-user code execution via undisclosed memory corruption
Published Mar 25, 2020 · Updated Aug 4, 2024
Memory corruption in Adobe Acrobat and Reader allows attackers to execute arbitrary code in the current user's context. Adobe does not disclose the affected code path, invalid memory operation, or malformed input that triggers the corruption. Affected releases span the Continuous, Classic 2017, and Classic 2015 tracks on Windows and macOS, and execution is limited to the privileges of the user running the application.
Summary
What happened
Memory corruption in Adobe Acrobat and Reader allows attackers to execute arbitrary code in the current user's context. Adobe does not disclose the affected code path, invalid memory operation, or malformed input that triggers the corruption. Affected releases span the Continuous, Classic 2017, and Classic 2015 tracks on Windows and macOS, and execution is limited to the privileges of the user running the application.
The record
- CVE
- CVE-2020-3797
- Published
- Mar 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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