User-context code execution via malicious file
Published Nov 12, 2024 · Updated Nov 13, 2024
Heap-based buffer overflow in Adobe InDesign 18.5.2 and earlier and 19.5 and earlier allows attackers to execute code via a malicious file. The public record does not identify the affected parser or disclose how file data causes an out-of-bounds heap write. Execution requires a local user to open the file and runs with that user's privileges, permitting compromise of the user's data and application session.
Summary
What happened
Heap-based buffer overflow in Adobe InDesign 18.5.2 and earlier and 19.5 and earlier allows attackers to execute code via a malicious file. The public record does not identify the affected parser or disclose how file data causes an out-of-bounds heap write. Execution requires a local user to open the file and runs with that user's privileges, permitting compromise of the user's data and application session.
The record
- CVE
- CVE-2024-49508
- Published
- Nov 12, 2024
- Updated
- Nov 13, 2024
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-787, CWE-122, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 13, 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.3
- Affected versionversion=0 <=19.5
- Affected versionversion=0 <=ID19.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