Current-user code execution via malicious file
Published Sep 11, 2023 · Updated Feb 27, 2025
Out-of-bounds write in Adobe InCopy 17.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, file format, or unchecked memory operation beyond classifying the flaw as an out-of-bounds write. Exploitation requires a victim to open the file, and successful code runs with that user's privileges.
Summary
What happened
Out-of-bounds write in Adobe InCopy 17.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, file format, or unchecked memory operation beyond classifying the flaw as an out-of-bounds write. Exploitation requires a victim to open the file, and successful code runs with that user's privileges.
The record
- CVE
- CVE-2022-28834
- Published
- Sep 11, 2023
- Updated
- Feb 27, 2025
- Vendor
- Adobe
- Product
- InCopy
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 27, 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 <=17.1
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