Code execution via malicious-file use-after-free
Published Feb 17, 2023 · Updated Mar 5, 2025
Use-after-free in Adobe Premiere Rush 2.6 and earlier allows attackers to execute code when a victim opens a malicious file. Adobe identifies the flaw class and malicious-file trigger but has not disclosed the affected parser, object lifetime error, or freed-memory reuse. Exploitation requires a victim to open the file and runs code in the current user’s context, permitting that account’s data and applications to be accessed or altered.
Summary
What happened
Use-after-free in Adobe Premiere Rush 2.6 and earlier allows attackers to execute code when a victim opens a malicious file. Adobe identifies the flaw class and malicious-file trigger but has not disclosed the affected parser, object lifetime error, or freed-memory reuse. Exploitation requires a victim to open the file and runs code in the current user’s context, permitting that account’s data and applications to be accessed or altered.
The record
- CVE
- CVE-2023-22244
- Published
- Feb 17, 2023
- Updated
- Mar 5, 2025
- Vendor
- Adobe
- Product
- Adobe Premiere Rush
- Classifications
- CWE-416, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2023CVE publishedPublication date reported by the CVE source.
- Mar 5, 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 <=2.6
- 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