IncopyApplication · Adobe

CVE-2022-28834

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 out-of-bounds write 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

Out-of-bounds write vulnerability in Adobe InCopy versions 17.1 and earlier, and 16.4.1 and earlier allows arbitrary code execution via a malicious file opened by the victim.

MitigationUpdate Adobe InCopy to the latest patched version and exercise caution when opening files from untrusted sources.

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 Adobe InCopy installation directory or application entry. On Windows, look in Program Files or check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\. On macOS, check /Applications for InCopy.app
    Affected if Adobe InCopy is not installed on the system, the vulnerability does not apply
  2. Determine installed InCopy version
    Open Adobe InCopy, then go to Help > About Adobe InCopy to display the version number. Alternatively, right-click the InCopy executable, select Properties, and view the Details tab for the version info
    Affected if The displayed version falls within 17.0 through 17.1, or is 16.4.1 or earlier
  3. Confirm version against affected ranges
    Compare your installed version number to these affected ranges: versions 17.0 through 17.1, and versions 16.4.1 and earlier
    Affected if Your version matches <= 16.4.1 OR (>= 17.0 AND <= 17.1)
  4. Assess user file-opening behavior
    Evaluate whether users in your environment typically open InCopy documents (.icml, .icml, .idml) from external or untrusted sources, as this is the required attack vector
    Affected if Users open files from untrusted or unknown sources, increasing the likelihood of exploitation

You are affected if Adobe InCopy versions 17.0-17.1 or 16.4.1 and earlier are installed AND users may open documents from untrusted sources.

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

Update Adobe InCopy to the latest patched version and exercise caution when opening files from untrusted sources.

Recommended fix Moderate confidence

Adobe InCopy 16.4.2 or later (16.x line); Adobe InCopy 17.2 or later (17.x line)

  1. 1. Close Adobe InCopy if it is currently running.
  2. 2. Open Adobe Creative Cloud desktop application or navigate to Adobe's official download page.
  3. 3. Check for available updates for Adobe InCopy.
  4. 4. If an update to version 16.4.2 or later (for the 16.x line) or version 17.2 or later (for the 17.x line) is available, download and install it.
  5. 5. After installation, verify the installed version by opening InCopy and navigating to Help > About InCopy to confirm the version number.
Caveat Standard minor version updates typically have minimal breaking changes; however, always review Adobe's release notes before updating production workflows.

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

Fix this in Incopy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-28834 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