Arbitrary code execution via buffer error
Published Jun 25, 2020 · Updated Aug 4, 2024
Adobe Acrobat and Reader through 2020.006.20042 allow attackers to execute arbitrary code via a buffer error. The affected buffer-handling locus and exact malformed input are not disclosed in the public advisory. Exploitation requires a victim to open attacker-controlled content, and execution occurs in the current user's context.
Summary
What happened
Adobe Acrobat and Reader through 2020.006.20042 allow attackers to execute arbitrary code via a buffer error. The affected buffer-handling locus and exact malformed input are not disclosed in the public advisory. Exploitation requires a victim to open attacker-controlled content, and execution occurs in the current user's context.
The record
- CVE
- CVE-2020-9604
- Published
- Jun 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 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.
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