Code execution via use-after-free
Published Sep 11, 2023 · Updated Feb 27, 2025
Use-after-free in Adobe InCopy 17.1 and earlier and 16.4.1 and earlier allows attackers to execute code through a malicious file. Adobe identifies the memory-lifetime error but has not published the affected component, freed object's reuse path, or triggering file structure. A victim must open the file, after which code runs with the current user's privileges on Windows or macOS.
Summary
What happened
Use-after-free in Adobe InCopy 17.1 and earlier and 16.4.1 and earlier allows attackers to execute code through a malicious file. Adobe identifies the memory-lifetime error but has not published the affected component, freed object's reuse path, or triggering file structure. A victim must open the file, after which code runs with the current user's privileges on Windows or macOS.
The record
- CVE
- CVE-2022-28835
- Published
- Sep 11, 2023
- Updated
- Feb 27, 2025
- Vendor
- Adobe
- Product
- InCopy
- Classifications
- CWE-416, 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.
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