dbcve.org
IndesignApplication · Adobe

CVE-2022-30665

HIGH · 7.8 CVSS v3.0 Published 2022-06-16
Fix available
A fix is available. Upgrade to after 17.2.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 InDesign versions 17.2.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

Adobe InDesign versions 17.2.1 and earlier and 16.4.1 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution when a victim opens a malicious InDesign file. This is a memory corruption issue that executes code in the context of the current user.

MitigationUpdate Adobe InDesign to version 17.3 or 16.4.2 or later to patch the vulnerability. Avoid opening untrusted InDesign files from unknown 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
IndesignApplication
Affected:<= 16.4.1>= 17.2.0, <= 17.2.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.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. Identify installed InDesign version on Windows
    Open the Windows Control Panel, go to Programs and Features, locate Adobe InDesign in the list, and note the version number displayed in the Version column
    Affected if The version listed is 16.4.1 or earlier, or falls within 17.2.0 to 17.2.1
  2. Identify installed InDesign version on macOS
    Open Finder, navigate to the Applications folder, right-click on Adobe InDesign, select Get Info, and read the Version number shown
    Affected if The version displayed is 16.4.1 or earlier, or falls within 17.2.0 to 17.2.1
  3. Check InDesign version from within the application
    Launch Adobe InDesign, click the Help menu, select About InDesign, and note the full version string shown in the about dialog
    Affected if The version string indicates 16.4.1 or earlier, or 17.2.0 through 17.2.1
  4. Compare version against affected ranges
    Verify that your installed version falls within one of these vulnerable ranges: all versions 16.4.1 and below, or versions 17.2.0 through 17.2.1
    Affected if Your installed version matches any of these ranges, meaning the out-of-bounds write vulnerability is present in your installation

You are affected if Adobe InDesign version 16.4.1 or earlier, or version 17.2.0 through 17.2.1, is installed on your system.

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.1
Interim mitigation

Update Adobe InDesign to version 17.3 or 16.4.2 or later to patch the vulnerability. Avoid opening untrusted InDesign files from unknown sources.

Recommended fix Moderate confidence

Adobe InDesign 16.4.2 or later for 16.x branch; Adobe InDesign 17.3 or later for 17.x branch

  1. 1. Verify current Adobe InDesign version by going to Help > About Adobe InDesign
  2. 2. For InDesign 16.x users: Upgrade to version 16.4.2 or later
  3. 3. For InDesign 17.x users: Upgrade to version 17.3 or later
  4. 4. Download the fixed version from the official Adobe website at helpx.adobe.com
  5. 5. Close any running instances of Adobe InDesign
  6. 6. Run the installer for the upgraded version
  7. 7. Restart InDesign after installation completes
  8. 8. Verify the installed version matches the patched release
Caveat Minor: Potential legacy plug-in compatibility issues with major version upgrades; verify plugin compatibility before production use

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

Fix this in Indesign 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-30665 — 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-30665 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