Code execution via malicious file input
Published Dec 10, 2024 · Updated Dec 17, 2024
Improper input validation in Adobe Animate 23.0.8 and earlier and 24.0.5 and earlier allows attackers to execute code via a malicious file. The public advisory identifies only improper validation during malicious-file processing and does not disclose the parser, file format, or erroneous operation. Execution requires a victim to open the file and runs with the victim’s current-user privileges, allowing arbitrary code in that account’s context.
Summary
What happened
Improper input validation in Adobe Animate 23.0.8 and earlier and 24.0.5 and earlier allows attackers to execute code via a malicious file. The public advisory identifies only improper validation during malicious-file processing and does not disclose the parser, file format, or erroneous operation. Execution requires a victim to open the file and runs with the victim’s current-user privileges, allowing arbitrary code in that account’s context.
The record
- CVE
- CVE-2024-52982
- Published
- Dec 10, 2024
- Updated
- Dec 17, 2024
- Vendor
- Adobe
- Product
- Adobe Animate
- Classifications
- CWE-20, T1204.002, 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.0.5
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