Code execution via dangerous-file handling
Published Oct 9, 2024 · Updated Oct 9, 2024
Unrestricted dangerous-file handling in Adobe InDesign 19.4 and earlier or 18.5.3 and earlier allows local users to execute arbitrary code. A crafted file passes the application's dangerous-file handling and reaches execution, but Adobe has not disclosed the responsible parser, file format, or missing validation. Exploitation requires user interaction; successful execution gains the application's security context.
Summary
What happened
Unrestricted dangerous-file handling in Adobe InDesign 19.4 and earlier or 18.5.3 and earlier allows local users to execute arbitrary code. A crafted file passes the application's dangerous-file handling and reaches execution, but Adobe has not disclosed the responsible parser, file format, or missing validation. Exploitation requires user interaction; successful execution gains the application's security context.
The record
- CVE
- CVE-2024-45137
- Published
- Oct 9, 2024
- Updated
- Oct 9, 2024
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-434, CAPEC-1, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 9, 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
What conditions does exploitation require?
What is affected?
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