Code execution via undisclosed memory corruption
Published Jan 29, 2020 · Updated Aug 4, 2024
Memory corruption in Adobe Illustrator CC 24.0 and earlier for Windows allows attackers to execute code as the current user. Adobe does not disclose the affected component, input format, or operation that corrupts memory. Exploitation requires local access and user interaction; successful code execution is confined to the current user's privileges.
Summary
What happened
Memory corruption in Adobe Illustrator CC 24.0 and earlier for Windows allows attackers to execute code as the current user. Adobe does not disclose the affected component, input format, or operation that corrupts memory. Exploitation requires local access and user interaction; successful code execution is confined to the current user's privileges.
The record
- CVE
- CVE-2020-3710
- Published
- Jan 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Adobe
- Product
- Adobe Illustrator
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=24.0 and earlier versions
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.
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