Arbitrary code execution via heap overflow
Published Feb 13, 2020 · Updated Aug 4, 2024
Heap overflow in affected Adobe Acrobat and Reader releases allows attackers to execute arbitrary code in the current user's context. Adobe has not published the affected parser or function, or how untrusted input causes the heap overwrite. The trigger and delivery path remain undisclosed, so exposure beyond execution with the current user's permissions cannot be bounded more precisely.
Summary
What happened
Heap overflow in affected Adobe Acrobat and Reader releases allows attackers to execute arbitrary code in the current user's context. Adobe has not published the affected parser or function, or how untrusted input causes the heap overwrite. The trigger and delivery path remain undisclosed, so exposure beyond execution with the current user's permissions cannot be bounded more precisely.
The record
- CVE
- CVE-2020-3742
- Published
- Feb 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 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