Code execution via malicious-file out-of-bounds write
Published Jul 12, 2023 · Updated Mar 5, 2025
Out-of-bounds write in Adobe InDesign ID18.3 and earlier and ID17.4.1 and earlier allows attackers to execute code through a malicious file. Adobe identifies an out-of-bounds write during malicious-file processing but has not disclosed the affected parser or the unchecked memory operation. Exploitation requires a victim to open the file, after which code runs with the current user's privileges.
Summary
What happened
Out-of-bounds write in Adobe InDesign ID18.3 and earlier and ID17.4.1 and earlier allows attackers to execute code through a malicious file. Adobe identifies an out-of-bounds write during malicious-file processing but has not disclosed the affected parser or the unchecked memory operation. Exploitation requires a victim to open the file, after which code runs with the current user's privileges.
The record
- CVE
- CVE-2023-29308
- Published
- Jul 12, 2023
- Updated
- Mar 5, 2025
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 12, 2023CVE publishedPublication date reported by the CVE source.
- Mar 5, 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 <=ID18.3
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