Code execution via malicious TTF file
Published Sep 1, 2021 · Updated Sep 17, 2024
Heap-based buffer overflow in Adobe Photoshop 21.2.10 and earlier and 22.4.3 and earlier allows attackers to execute code via a malicious TTF file. The public record identifies a malicious TTF file but does not disclose the parser routine or the malformed field whose handling overruns heap memory. A victim must open the file; successful exploitation runs arbitrary code with the current user’s privileges on Windows or macOS.
Summary
What happened
Heap-based buffer overflow in Adobe Photoshop 21.2.10 and earlier and 22.4.3 and earlier allows attackers to execute code via a malicious TTF file. The public record identifies a malicious TTF file but does not disclose the parser routine or the malformed field whose handling overruns heap memory. A victim must open the file; successful exploitation runs arbitrary code with the current user’s privileges on Windows or macOS.
The record
- CVE
- CVE-2021-36065
- Published
- Sep 1, 2021
- Updated
- Sep 17, 2024
- Vendor
- Adobe
- Product
- Adobe Photoshop
- Classifications
- CWE-122, CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2021CVE publishedPublication date reported by the CVE source.
- Sep 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=unspecified <=21.2.10
- Affected versionversion=unspecified <=22.4.3
- Affected versionversion=unspecified <=None
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