dbcve.org
IncopyApplication · Adobe

CVE-2022-30652

HIGH · 7.8 CVSS v3.0 Published 2022-06-16
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 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

This is an out-of-bounds write vulnerability in Adobe InCopy versions 17.2 and earlier and 16.4.1 and earlier. The vulnerability allows arbitrary code execution in the context of the current user through memory corruption. Exploitation requires a victim to open a specially crafted malicious file, typically delivered via social engineering or phishing.

MitigationUpdate Adobe InCopy to version 17.3 or 16.4.2 or later to remediate this vulnerability. Additionally, educate users to 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.0/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. Confirm Adobe InCopy is installed
    Check for InCopy installation via program files directory, Start menu, or Add/Remove Programs list. Look for 'Adobe InCopy' in the list of installed applications.
    Affected if Adobe InCopy is not found on the system, the CVE does not apply.
  2. Locate the installed InCopy executable
    Navigate to the InCopy installation folder (typically C:\Program Files\Adobe\Adobe InCopy version\ or C:\Program Files (x86)\Adobe\Adobe InCopy version\) and locate the InCopy executable file.
    Affected if The executable InCopy.exe exists, indicating InCopy is installed.
  3. Determine the installed version number
    Right-click the InCopy.exe file, select Properties, then go to the Details tab to view the File Version. Alternatively, open InCopy and go to Help > About Adobe InCopy to display the version information.
    Affected if The version displayed is the installed version that must be compared to the affected ranges.
  4. Compare version against affected ranges
    Review the version from the previous step. Affected versions are: 16.4.1 and earlier, and any version from 17.0 through 17.2. Compare your installed version to these ranges.
    Affected if The installed version is 16.4.1 or lower, OR is 17.0, 17.1, or 17.2 - the system is running a vulnerable version.

If Adobe InCopy is installed and the version falls within 16.4.1 and earlier or 17.0 through 17.2, the environment is vulnerable to CVE-2022-30652.

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 16.4.2 or later to remediate this vulnerability. Additionally, educate users to avoid opening files from untrusted sources.

Recommended fix Moderate confidence

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

  1. 1. Close any running instances of Adobe InCopy
  2. 2. Back up any important InCopy documents as a precautionary measure
  3. 3. Open Adobe Creative Cloud desktop application or navigate to the Adobe InCopy product page
  4. 4. Look for the Updates section or check for available updates to InCopy
  5. 5. Update to version 17.3 or later (for 17.x line) or version 16.4.2 or later (for 16.x line)
  6. 6. After installation, verify the updated version by opening InCopy and checking Help > About InCopy
Caveat As this is a minor version update within the same major release, significant breaking changes are unlikely; however, test critical workflows with the new version before deploying organization-wide

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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