Code execution via undisclosed heap buffer overflow
Published Jun 16, 2022 · Updated Apr 23, 2025
Heap-based buffer overflow in Adobe InDesign 17.2.1 and earlier and 16.4.1 and earlier allows attackers to execute code via a malicious file. Adobe has not disclosed the affected parser or the operation that writes beyond the heap buffer. A local user must open the crafted file; successful exploitation runs code in that user's context.
Summary
What happened
Heap-based buffer overflow in Adobe InDesign 17.2.1 and earlier and 16.4.1 and earlier allows attackers to execute code via a malicious file. Adobe has not disclosed the affected parser or the operation that writes beyond the heap buffer. A local user must open the crafted file; successful exploitation runs code in that user's context.
The record
- CVE
- CVE-2022-30658
- Published
- Jun 16, 2022
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=unspecified <=16.4.1
- Affected versionversion=unspecified <=17.2.1
- Affected versionversion=unspecified <=None
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