CVE-2022-30659
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 · uneditedAdobe 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 confidenceAdobe 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 user opens a maliciously crafted InDesign file. The vulnerability is triggered due to improper memory handling during file parsing.
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<= 16.4.1>= 17.2.0, <= 17.2.1CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Locate installed Adobe InDesign versionOpen Adobe InDesign and go to Help > About InDesign (Windows) or InDesign > About InDesign (macOS). Alternatively, on Windows check Add/Remove Programs or the application's executable properties. On macOS, right-click the application in Applications folder and select Get Info.Affected if The displayed version is 16.4.1 or earlier, or falls within 17.2.0 to 17.2.1.
-
Confirm affected version via command lineOn Windows, open Command Prompt and run: reg query 'HKLM\SOFTWARE\Adobe\InDesign\InstallDetails' /v 'Version' 2>nul. On macOS, run: defaults read /Applications/Adobe\ InDesign\*/Adobe\ InDesign\*/Info CFBundleShortVersionStringAffected if The queried version matches the affected ranges.
-
Identify all installed InDesign releasesOn Windows, open Programs and Features (Add or Remove Programs) and look for all Adobe InDesign entries. On macOS, open Terminal and run: ls /Applications | grep -i 'InDesign'Affected if Any listed InDesign version is 16.4.1 or earlier, or between 17.2.0 and 17.2.1.
If any installed Adobe InDesign version is 16.4.1 or earlier, or 17.2.0 through 17.2.1, the environment is vulnerable to this CVE.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate Adobe InDesign to version 17.3 or later (for 17.x) or 16.4.2 or later (for 16.x). Avoid opening InDesign files from untrusted sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30659 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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