Arbitrary code execution via malicious M4A parsing
Published Jun 13, 2022 · Updated Apr 23, 2025
Out-of-bounds write in Adobe Premiere Pro 15.4 and earlier allows remote attackers to execute code when a user opens a malicious M4A file. The M4A parser writes past the end of a memory buffer while processing crafted file data, although Adobe has not named the affected routine. A user must open the file, after which attacker-controlled code runs with that user's application privileges.
Summary
What happened
Out-of-bounds write in Adobe Premiere Pro 15.4 and earlier allows remote attackers to execute code when a user opens a malicious M4A file. The M4A parser writes past the end of a memory buffer while processing crafted file data, although Adobe has not named the affected routine. A user must open the file, after which attacker-controlled code runs with that user's application privileges.
The record
- CVE
- CVE-2021-46816
- Published
- Jun 13, 2022
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- Premiere
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 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
- 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