User-assisted code execution via out-of-bounds buffer access
Published Mar 16, 2022 · Updated Apr 23, 2025
Memory corruption in Adobe Premiere Pro 15.4.1 and earlier allows context-dependent attackers to execute code through a malicious file. Adobe identifies an access after the end of a buffer during malicious-file handling but does not disclose the parser or code path. A user must open the file, after which code executes with the current user's privileges.
Summary
What happened
Memory corruption in Adobe Premiere Pro 15.4.1 and earlier allows context-dependent attackers to execute code through a malicious file. Adobe identifies an access after the end of a buffer during malicious-file handling but does not disclose the parser or code path. A user must open the file, after which code executes with the current user's privileges.
The record
- CVE
- CVE-2021-40792
- Published
- Mar 16, 2022
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- Premiere
- Classifications
- CWE-788, CWE-119, 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