Code execution via out-of-bounds GIF parsing
Published May 16, 2024 · Updated Aug 2, 2024
Out-of-bounds writing in Adobe FrameMaker 2020 Update 5 and earlier and 2022 Update 3 and earlier allows attackers to run code from a malicious GIF. Adobe identifies the locus as GIF-file parsing that writes outside an allocated buffer but does not disclose the responsible parser routine or malformed field. Exploitation requires a local FrameMaker user to open the file, after which code runs with that user's privileges.
Summary
What happened
Out-of-bounds writing in Adobe FrameMaker 2020 Update 5 and earlier and 2022 Update 3 and earlier allows attackers to run code from a malicious GIF. Adobe identifies the locus as GIF-file parsing that writes outside an allocated buffer but does not disclose the responsible parser routine or malformed field. Exploitation requires a local FrameMaker user to open the file, after which code runs with that user's privileges.
The record
- CVE
- CVE-2024-30292
- Published
- May 16, 2024
- Updated
- Aug 2, 2024
- Vendor
- Adobe
- Product
- Adobe FrameMaker
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <=2022.3
- Affected versionversion=2020 <update_5
- Affected versionversion=2022 <update_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