Code execution via crafted-file out-of-bounds write
Published Dec 10, 2024 · Updated Dec 17, 2024
Out-of-bounds write in Adobe Media Encoder 25.0, 24.6.3 and earlier allows attackers to execute code as the current user via a malicious file. Adobe identifies the fault only as an out-of-bounds write reached while processing the file and does not disclose the affected parser or memory operation. Opening the file is required; successful exploitation runs arbitrary code with the victim's current-user privileges.
Summary
What happened
Out-of-bounds write in Adobe Media Encoder 25.0, 24.6.3 and earlier allows attackers to execute code as the current user via a malicious file. Adobe identifies the fault only as an out-of-bounds write reached while processing the file and does not disclose the affected parser or memory operation. Opening the file is required; successful exploitation runs arbitrary code with the victim's current-user privileges.
The record
- CVE
- CVE-2024-49551
- Published
- Dec 10, 2024
- Updated
- Dec 17, 2024
- Vendor
- Adobe
- Product
- Adobe Media Encoder
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 2024CVE publishedPublication date reported by the CVE source.
- Dec 17, 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=0 <=24.6.3
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.
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