dbcve.org
IncopyApplication · Adobe

CVE-2022-34250

HIGH · 7.8 CVSS v3.1 Published 2022-07-15
Fix available
A fix is available. Upgrade to after 17.2 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.2 (and earlier) and 16.4.1 (and earlier) are affected by a Heap-based Buffer Overflow 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 · moderate confidence

Adobe InCopy versions 17.2 and earlier and 16.4.1 and earlier contain a heap-based buffer overflow vulnerability. When a victim opens a specially crafted malicious file, the heap overflow occurs and can be leveraged for arbitrary code execution in the context of the current user.

MitigationUpdate Adobe InCopy to version 17.3 or later (for the 17.x branch) or version 16.4.2 or later (for the 16.x branch). Until patched, avoid 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.2

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 installation in typical locations such as C:\Program Files\Adobe\Adobe InCopy 2022 or C:\Program Files\Adobe\Adobe InCopy 2023, or look for the InCopy application in the Windows Start Menu.
    Affected if Adobe InCopy is present on the system
  2. Determine installed InCopy version
    Right-click the InCopy executable (usually named INCOPY.EXE), select Properties, and view the Version tab. Alternatively, open InCopy, go to Help > About InCopy to display the version number.
    Affected if The displayed version falls within the affected ranges: 16.4.1 or earlier, or 17.0 through 17.2
  3. Compare version to CVE affected ranges
    Cross-reference the installed version number with the vulnerable ranges: versions 16.4.1 and earlier, and versions 17.0 through 17.2 are affected.
    Affected if The installed version is 16.4.1 or lower, OR is 17.0, 17.1, or 17.2
  4. Assess file handling behavior
    Determine if the user or other users on the system open InCopy files from untrusted or unknown sources, as exploitation requires opening a specially crafted malicious file.
    Affected if The vulnerable version is installed AND the system routinely opens InCopy documents from untrusted or external sources

A user is affected if Adobe InCopy version 16.4.1 or earlier or version 17.0-17.2 is installed AND the user opens maliciously crafted InCopy files 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.2
Interim mitigation

Update Adobe InCopy to version 17.3 or later (for the 17.x branch) or version 16.4.2 or later (for the 16.x branch). Until patched, avoid opening files from untrusted sources.

Recommended fix Moderate confidence

Adobe InCopy version 17.3 or later

  1. 1. Close Adobe InCopy if it is currently running
  2. 2. Open a web browser and navigate to the Adobe InCopy download page at helpx.adobe.com
  3. 3. Download the latest version of Adobe InCopy (version 17.3 or later)
  4. 4. Run the installer and follow the on-screen prompts to complete the installation
  5. 5. After installation, verify the version by opening InCopy and navigating to Help > About InCopy to confirm the version number is 17.3 or higher
  6. 6. Alternatively, use Adobe Creative Cloud desktop application to update InCopy to the latest version
Caveat Standard Adobe update; ensure Creative Cloud subscription is active for automatic updates

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

Fix this in Incopy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34250 — 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-34250 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