dbcve.org
IndesignApplication · Adobe

CVE-2022-30660

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

Out-of-bounds write vulnerability in Adobe InDesign versions 17.2.1/16.4.1 and earlier allows arbitrary code execution when a user opens a maliciously crafted InDesign file, due to improper bounds checking during file parsing.

MitigationUpdate Adobe InDesign to version 17.2.2 or later (17.x) and 16.4.2 or later (16.x); enforce user awareness to 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 Control Panel > Programs and Features, locate Adobe InDesign in the list, and note the version number shown 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 inclusive
  2. Identify installed InDesign version on macOS
    Open Finder > Applications > Adobe InDesign, right-click the application, select Get Info, and read the Version number under General Information
    Affected if The version shown is 16.4.1 or earlier, or falls within 17.2.0 to 17.2.1 inclusive
  3. Check InDesign version from within the application
    Launch Adobe InDesign, go to Help > About Adobe InDesign (Windows) or InDesign > About InDesign (Mac), and read the version string displayed in the dialog box
    Affected if The version string matches 16.4.1 or earlier, or shows a build between 17.2.0 and 17.2.1
  4. Determine if users open InDesign files from external or untrusted sources
    Review your organization's security policies or endpoint monitoring for recent InDesign file openings, particularly files received via email, downloads, or from unknown external sources
    Affected if Users in your environment open InDesign files from untrusted or unknown sources while running a vulnerable version

Your environment is affected if Adobe InDesign version 16.4.1 or earlier, or version 17.2.0 through 17.2.1 is installed and users may open untrusted InDesign 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.2.1
Interim mitigation

Update Adobe InDesign to version 17.2.2 or later (17.x) and 16.4.2 or later (16.x); enforce user awareness to avoid opening untrusted InDesign files from unknown sources.

Recommended fix Moderate confidence

InDesign 16.4.2+ or InDesign 17.3+ (depending on major version in use)

  1. 1. Open Adobe Creative Cloud desktop application or Adobe InDesign
  2. 2. Check for available updates in the Updates tab
  3. 3. If using InDesign 16.x: upgrade to version 16.4.2 or later
  4. 4. If using InDesign 17.x: upgrade to version 17.3 or later (17.3.0 or newer)
  5. 5. Restart the application after updating
  6. 6. Verify the installed version matches a fixed release (16.4.2+ or 17.3+)
Caveat Upgrade within same major version typically safe; ensure backup of critical InDesign files before updating

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

Fix this in Indesign Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,500
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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