Arbitrary code execution via out-of-bounds write
Published Mar 25, 2020 · Updated Aug 4, 2024
An out-of-bounds write in affected Adobe Acrobat and Reader releases allows attackers to execute arbitrary code in the current user's context. Adobe identifies the corrupting operation only as an out-of-bounds write and does not disclose the affected parser, file format, buffer, or input field. The affected 2015, 2017, and Continuous tracks run on Windows and macOS; Adobe has not published the input vector or interaction needed to reach the write.
Summary
What happened
An out-of-bounds write in affected Adobe Acrobat and Reader releases allows attackers to execute arbitrary code in the current user's context. Adobe identifies the corrupting operation only as an out-of-bounds write and does not disclose the affected parser, file format, buffer, or input field. The affected 2015, 2017, and Continuous tracks run on Windows and macOS; Adobe has not published the input vector or interaction needed to reach the write.
The record
- CVE
- CVE-2020-3795
- 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