Code execution via malicious file out-of-bounds access
Published Mar 16, 2022 · Updated Apr 23, 2025
Memory corruption in Adobe Media Encoder 15.4.1 and earlier allows context-dependent attackers to execute code via a malicious file. Adobe identifies access beyond the end of a memory buffer but has not published the affected parser, file format, or malformed field that triggers the access. Exploitation requires a user to open the file, and successful code runs with that user's privileges.
Summary
What happened
Memory corruption in Adobe Media Encoder 15.4.1 and earlier allows context-dependent attackers to execute code via a malicious file. Adobe identifies access beyond the end of a memory buffer but has not published the affected parser, file format, or malformed field that triggers the access. Exploitation requires a user to open the file, and successful code runs with that user's privileges.
The record
- CVE
- CVE-2021-40779
- Published
- Mar 16, 2022
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- Adobe Media Encoder
- Classifications
- CWE-788, CWE-119, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 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=unspecified <=15.4.1
- 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.
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