Code execution via undisclosed memory corruption
Published Jun 26, 2020 · Updated Aug 4, 2024
Memory corruption in Adobe Illustrator 24.0.2 and earlier allows attackers to execute arbitrary code after user interaction. Adobe has not disclosed the affected parser or the memory operation that mishandles input data. Code executes in the current user's context, and no public detail identifies the content or action needed to trigger the flaw.
Summary
What happened
Memory corruption in Adobe Illustrator 24.0.2 and earlier allows attackers to execute arbitrary code after user interaction. Adobe has not disclosed the affected parser or the memory operation that mishandles input data. Code executes in the current user's context, and no public detail identifies the content or action needed to trigger the flaw.
The record
- CVE
- CVE-2020-9572
- Published
- Jun 26, 2020
- Updated
- Aug 4, 2024
- Vendor
- Adobe
- Product
- Adobe Illustrator
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 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.2 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