dbcve.org
IncopyApplication · Adobe

CVE-2022-28835

HIGH · 7.8 CVSS v3.1 Published 2023-09-11
Fix available
A fix is available. Upgrade to after 17.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe InCopy versions 17.1 (and earlier) and 16.4.1 (and earlier) are affected by an Use-After-Free vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe InCopy versions 17.1 and earlier and 16.4.1 and earlier contain a Use-After-Free vulnerability that allows arbitrary code execution in the current user's context. Successful exploitation requires the victim to open a specially crafted malicious file.

MitigationUsers should not open untrusted or unexpected files and should update to the latest patched version of Adobe InCopy. Organizations should deploy the security update through their endpoint management systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IncopyApplication
Affected:<= 16.4.1>= 17.0, <= 17.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Adobe InCopy is installed
    Check for InCopy.exe in typical installation paths such as C:\Program Files\Adobe\Adobe InCopy 2022\ or C:\Program Files (x86)\Adobe\Adobe InCopy 2022\, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\InCopy.exe
    Affected if InCopy executable exists on the system
  2. Retrieve installed InCopy version number
    Right-click InCopy.exe, select Properties, then view the Details tab for Product Version, or run: wmic product where "name like '%InCopy%'" get version
    Affected if Version cannot be determined or is within the affected range
  3. Compare version against affected ranges
    Compare your installed version to the vulnerable ranges: 16.4.1 and earlier, or 17.0 through 17.1
    Affected if Installed version is 16.4.1 or lower, OR is 17.0, 17.1, or any version between 17.0 and 17.1
  4. Assess user interaction risk
    Determine whether users in your environment typically open files from untrusted or external sources, as exploitation requires opening a specially crafted malicious file
    Affected if Users open untrusted or unexpected files received via email, downloads, or removable media

User is affected if Adobe InCopy version 16.4.1 or earlier, or version 17.0 through 17.1 is installed and users may open untrusted files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 17.1
Interim mitigation

Users should not open untrusted or unexpected files and should update to the latest patched version of Adobe InCopy. Organizations should deploy the security update through their endpoint management systems.

Recommended fix Moderate confidence

Adobe InCopy 17.2 or later (or latest available version)

  1. Verify current InCopy version by opening InCopy and navigating to Help > About InCopy
  2. Download the latest version of Adobe InCopy from the official Adobe website (get.adobe.com/incopy) or through the Creative Cloud desktop application
  3. Close any running instances of Adobe InCopy
  4. Install the updated version, which will be version 17.2 or later (beyond the affected 17.1 and earlier versions)
  5. After installation, confirm the new version number matches the fixed release
Caveat Adobe updates typically include feature changes; review release notes for notable changes before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Incopy Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28835 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28835 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data