Application crash via null pointer dereference
Published Mar 11, 2025 · Updated Mar 11, 2025
NULL pointer dereference in Adobe InDesign Desktop 20.1 and 19.5.2 and earlier allows attackers to crash the application with a crafted file. Adobe identifies a null pointer dereference during malicious-file processing but has not published the affected parser, file format, or invalid pointer operation. Exploitation requires user interaction to open the crafted file, and the documented consequence is an application crash rather than code execution or data disclosure.
Summary
What happened
NULL pointer dereference in Adobe InDesign Desktop 20.1 and 19.5.2 and earlier allows attackers to crash the application with a crafted file. Adobe identifies a null pointer dereference during malicious-file processing but has not published the affected parser, file format, or invalid pointer operation. Exploitation requires user interaction to open the crafted file, and the documented consequence is an application crash rather than code execution or data disclosure.
The record
- CVE
- CVE-2025-27176
- Published
- Mar 11, 2025
- Updated
- Mar 11, 2025
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-476, T1499.004, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2025CVE publishedPublication date reported by the CVE source.
- Mar 11, 2025Record 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 <=ID19.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