Current-user code execution via crafted SVG processing
Published Jun 25, 2020 · Updated Aug 4, 2024
Memory corruption in Adobe Illustrator 24.1.2 and earlier allows attackers to execute code as the current user through a crafted SVG file. Illustrator's SVG-processing path corrupts memory while parsing attacker-controlled content; Adobe and Fortinet do not identify the faulty function or precise memory operation. Execution requires a user to open the malicious file, and resulting code runs with that user's privileges rather than crossing an independent privilege boundary.
Summary
What happened
Memory corruption in Adobe Illustrator 24.1.2 and earlier allows attackers to execute code as the current user through a crafted SVG file. Illustrator's SVG-processing path corrupts memory while parsing attacker-controlled content; Adobe and Fortinet do not identify the faulty function or precise memory operation. Execution requires a user to open the malicious file, and resulting code runs with that user's privileges rather than crossing an independent privilege boundary.
The record
- CVE
- CVE-2020-9640
- Published
- Jun 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Adobe
- Product
- Adobe Illustrator
- Classifications
- CWE-787, T1203, T1204.002
- 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=24.1.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.
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