Code execution via malicious-file heap overflow
Published Aug 14, 2024 · Updated Aug 16, 2024
Heap-based buffer overflow in Adobe InDesign 19.4 and 18.5.2 and earlier allows attackers to execute code via a malicious file. Adobe identifies heap memory corruption during malicious-file processing but has not published the affected parser, field, or unchecked operation. Opening the file is required, after which code runs with the current user's privileges on Windows or macOS.
Summary
What happened
Heap-based buffer overflow in Adobe InDesign 19.4 and 18.5.2 and earlier allows attackers to execute code via a malicious file. Adobe identifies heap memory corruption during malicious-file processing but has not published the affected parser, field, or unchecked operation. Opening the file is required, after which code runs with the current user's privileges on Windows or macOS.
The record
- CVE
- CVE-2024-41853
- Published
- Aug 14, 2024
- Updated
- Aug 16, 2024
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-122, CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 16, 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 <=18.5.2
- Affected versionversion=0 <=19.4
- Affected versionversion=0 <=ID18.5.2
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