dbcve.org
IndesignApplication · Adobe

CVE-2022-30658

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 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 · high confidence

Adobe InDesign versions 17.2.1/16.4.1 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a maliciously crafted InDesign file (.indd). Successful exploitation allows arbitrary code execution in the context of the current user.

MitigationUpdate InDesign to version 17.3 and 16.5 or later. Avoid opening untrusted or unexpected 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 column. Alternatively, navigate to the InDesign installation directory (typically C:\Program Files\Adobe\Adobe InDesign <version>), right-click InDesign.exe, select Properties, and view the Product Version in the Details tab.
    Affected if The version shown is 16.4.1 or lower, or is 17.2.0 or 17.2.1
  2. Verify the exact InDesign version number
    Launch InDesign, go to Help > About Adobe InDesign. The version number displayed in the dialog (for example, 16.4.1 or 17.2.1) confirms the precise installed build.
    Affected if The About dialog reports version 16.4.1 or any version below 16.5, or reports version 17.2.0 or 17.2.1
  3. Check for InDesign 17.x installation
    If you have multiple versions installed, identify which version(s) are present by examining the folder names under C:\Program Files\Adobe\ (such as Adobe InDesign 2022 for v16.x or Adobe InDesign 2023 for v17.x).
    Affected if A folder named Adobe InDesign 2023 exists and contains InDesign.exe version 17.2.0 or 17.2.1

You are affected if any installed instance of Adobe InDesign is version 16.4.1 or earlier, or version 17.2.0 or 17.2.1.

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 InDesign to version 17.3 and 16.5 or later. Avoid opening untrusted or unexpected InDesign files from unknown sources.

Recommended fix Moderate confidence

InDesign 16.5 or later for 16.x branch; InDesign 17.3 or later for 17.x branch

  1. 1. Close Adobe InDesign if it is currently running.
  2. 2. Open Adobe Creative Cloud desktop application or navigate to the Adobe InDesign download page.
  3. 3. Locate Adobe InDesign in your installed applications.
  4. 4. Click Update or check for updates to download and install the latest version.
  5. 5. Alternatively, download InDesign version 16.5 or later for the 16.x branch, or version 17.3 or later for the 17.x branch from Adobe's official website.
  6. 6. Run the installer and follow the on-screen prompts to complete the installation.
  7. 7. After installation, verify the installed version matches a fixed release (16.5+, 17.3+).
  8. 8. Do not open any untrusted or suspicious InDesign files until the update is applied.
Caveat Minor release upgrade with typical compatibility; review Adobe's release notes for any document format or script changes

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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