Application crash via malicious file null dereference
Published Nov 16, 2023 · Updated Aug 2, 2024
A NULL pointer dereference in Adobe InDesign 18.5 and 17.4.2 and earlier allows attackers to crash the application via a malicious file. Adobe has not disclosed the affected file parser or the operation that dereferences the null pointer. Exploitation requires a victim to open the file and interrupts only that InDesign process in the current user's context.
Summary
What happened
A NULL pointer dereference in Adobe InDesign 18.5 and 17.4.2 and earlier allows attackers to crash the application via a malicious file. Adobe has not disclosed the affected file parser or the operation that dereferences the null pointer. Exploitation requires a victim to open the file and interrupts only that InDesign process in the current user's context.
The record
- CVE
- CVE-2023-44341
- Published
- Nov 16, 2023
- Updated
- Aug 2, 2024
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 16, 2023CVE 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 <=ID18.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.
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