Arbitrary code execution via malicious TIFF out-of-bounds write
Published Jun 15, 2022 · Updated Apr 23, 2025
Out-of-bounds write in Adobe InDesign allows attackers to execute code in the current user's context via a malicious TIFF file. InDesign's TIFF-processing path writes beyond a buffer boundary while handling crafted image data, but Adobe has not disclosed the responsible function or malformed field. A user must open or otherwise process the file; successful exploitation runs attacker-controlled code with that user's privileges.
Summary
What happened
Out-of-bounds write in Adobe InDesign allows attackers to execute code in the current user's context via a malicious TIFF file. InDesign's TIFF-processing path writes beyond a buffer boundary while handling crafted image data, but Adobe has not disclosed the responsible function or malformed field. A user must open or otherwise process the file; successful exploitation runs attacker-controlled code with that user's privileges.
The record
- CVE
- CVE-2021-39820
- Published
- Jun 15, 2022
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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 <=16.3.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.
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