dbcve.org
IndesignApplication · Adobe

CVE-2022-30676

MEDIUM · 5.5 CVSS v3.1 Published 2022-09-16
Fix available
A fix is available. Upgrade to after 17.3 or later.
See remediation →
58/100
Remediation priority · Elevated
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 16.4.2 (and earlier) and 17.3 (and earlier) are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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

An out-of-bounds read vulnerability exists in Adobe InDesign versions 16.4.2 and earlier, and 17.3 and earlier. The vulnerability allows reading memory beyond allocated boundaries, potentially exposing sensitive information such as memory addresses. This information disclosure can be leveraged to bypass ASLR mitigation, making other exploits more reliable. Exploitation requires user interaction—the victim must open a malicious InDesign file.

MitigationUpdate Adobe InDesign to the latest patched version released by Adobe. Until patched, instruct users to avoid opening InDesign files from untrusted or 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.0, <= 16.4.2>= 17.0, <= 17.3

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 InDesign is installed
    Check your system for Adobe InDesign installation. On Windows, look in Program Files or use the 'Programs and Features' control panel. On macOS, check the Applications folder.
    Affected if InDesign is not installed on the system, the CVE does not apply.
  2. Determine the installed InDesign version
    Locate the InDesign application and check its version. On Windows, right-click the InDesign executable and select Properties, then view the Details tab for version information. On macOS, right-click the application, select Get Info, and check the Version field.
    Affected if Unable to determine the version means the check is inconclusive.
  3. Compare against affected version ranges
    Compare your installed version number to the affected ranges: 16.0 through 16.4.2, and 17.0 through 17.3. If your version falls within either range, the environment is potentially affected.
    Affected if The installed version is 16.0-16.4.2 or 17.0-17.3 inclusive.
  4. Assess user interaction risk
    Recall that exploitation requires a user to open a malicious InDesign file. Evaluate whether users in your environment commonly open InDesign files from external or untrusted sources.
    Affected if Users routinely open InDesign files from untrusted sources, increasing exploitation likelihood.

You are affected if Adobe InDesign is installed and the installed version falls within 16.0-16.4.2 or 17.0-17.3, especially if users may open 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.3
Interim mitigation

Update Adobe InDesign to the latest patched version released by Adobe. Until patched, instruct users to avoid opening InDesign files from untrusted or unknown sources.

Recommended fix High confidence

InDesign 16.4.3 or later for the 16.x branch; InDesign 17.4 or later for the 17.x branch

  1. 1. Close Adobe InDesign if it is currently running
  2. 2. Back up any important InDesign files and templates
  3. 3. Open Adobe Creative Cloud desktop application or navigate to adobe.com/downloads
  4. 4. Locate Adobe InDesign in your installed applications
  5. 5. Check for available updates - the fix is available in InDesign versions 16.4.3 and 17.4 and later
  6. 6. Download and install the available security update
  7. 7. After installation, verify the version by opening InDesign and going to Help > About InDesign
  8. 8. Confirm the installed version is 16.4.3 or higher, or 17.4 or higher
Caveat Standard minor version upgrades typically have minimal breaking changes; however, test critical workflows and custom scripts after updating

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

Fix this in Indesign Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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