Code execution via malicious file opening
Published Dec 10, 2024 · Updated Dec 17, 2024
Out-of-bounds write in Adobe Illustrator 29.0.0 and 28.7.2 and earlier allows attackers to execute code via a malicious file. Adobe has not disclosed the affected file parser, memory buffer, or the operation that writes beyond its bounds. A victim must open the crafted file, after which code executes with the privileges of the current user.
Summary
What happened
Out-of-bounds write in Adobe Illustrator 29.0.0 and 28.7.2 and earlier allows attackers to execute code via a malicious file. Adobe has not disclosed the affected file parser, memory buffer, or the operation that writes beyond its bounds. A victim must open the crafted file, after which code executes with the privileges of the current user.
The record
- CVE
- CVE-2024-49538
- Published
- Dec 10, 2024
- Updated
- Dec 17, 2024
- Vendor
- Adobe
- Product
- Illustrator
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 2024CVE publishedPublication date reported by the CVE source.
- Dec 17, 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=0 <=28.7.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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