Code execution via M4A out-of-bounds access
Published Mar 16, 2022 · Updated Sep 16, 2024
Memory corruption in Adobe Character Animator 4.4 and earlier allows context-dependent attackers to execute arbitrary code via a crafted M4A file. The M4A parser accesses memory beyond the end of a buffer while processing file data, corrupting process memory. Exploitation requires a user to open the malicious file, and successful code runs with that user's privileges.
Summary
What happened
Memory corruption in Adobe Character Animator 4.4 and earlier allows context-dependent attackers to execute arbitrary code via a crafted M4A file. The M4A parser accesses memory beyond the end of a buffer while processing file data, corrupting process memory. Exploitation requires a user to open the malicious file, and successful code runs with that user's privileges.
The record
- CVE
- CVE-2021-40765
- Published
- Mar 16, 2022
- Updated
- Sep 16, 2024
- Vendor
- Adobe
- Product
- Adobe Character Animator
- Classifications
- CWE-119, CWE-788, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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 <=4.4
- 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