Code execution via out-of-bounds memory write
Published Jun 15, 2022 · Updated Apr 23, 2025
Out-of-bounds write in Adobe Media Encoder 22.0 and earlier and 15.4.2 and earlier allows attackers to execute code via a malicious file. Adobe has not published the affected file parser or the buffer operation that writes beyond its allocation. A victim must open the crafted file; successful exploitation runs code with the current user's privileges on Windows or macOS.
Summary
What happened
Out-of-bounds write in Adobe Media Encoder 22.0 and earlier and 15.4.2 and earlier allows attackers to execute code via a malicious file. Adobe has not published the affected file parser or the buffer operation that writes beyond its allocation. A victim must open the crafted file; successful exploitation runs code with the current user's privileges on Windows or macOS.
The record
- CVE
- CVE-2021-43756
- Published
- Jun 15, 2022
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- Adobe Media Encoder
- Classifications
- CWE-787, T1204.002
- 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 <=15.4.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