Code execution via out-of-bounds write
Published Aug 24, 2021 · Updated Apr 23, 2025
Out-of-bounds write in Adobe After Effects 18.2 and earlier allows attackers to execute code by inducing a user to open a crafted file. The file parser writes beyond an allocated memory boundary while processing attacker-controlled file data, corrupting memory in the current user's process. Adobe's affected-version table limits the flaw to Windows, and exploitation requires user interaction; code runs with the current user's privileges.
Summary
What happened
Out-of-bounds write in Adobe After Effects 18.2 and earlier allows attackers to execute code by inducing a user to open a crafted file. The file parser writes beyond an allocated memory boundary while processing attacker-controlled file data, corrupting memory in the current user's process. Adobe's affected-version table limits the flaw to Windows, and exploitation requires user interaction; code runs with the current user's privileges.
The record
- CVE
- CVE-2021-28602
- Published
- Aug 24, 2021
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- After Effects
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2021CVE 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=unspecified <=18.2
- Affected versionversion=unspecified <=None
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