dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-30674

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

An out-of-bounds read vulnerability in Adobe InDesign versions 16.4.2/17.3 and earlier allows a specially crafted malicious file to read memory beyond intended bounds when opened by a victim, potentially exposing sensitive memory contents and enabling bypass of ASLR mitigations.

MitigationUpdate Adobe InDesign to the patched versions (16.4.3+ for desktop, 17.4+ for subscription) and exercise caution when opening files from untrusted 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
FedoraOperating system
Affected:= 35= 36= 37
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. Locate installed Adobe InDesign version
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\InDesign\DetectVersion or check via Help > About Adobe InDesign in the application. On macOS, right-click the InDesign application in Applications folder and select Get Info to view the version number.
    Affected if Version number cannot be determined or application is not installed (detection incomplete)
  2. Compare version against affected 16.x range
    If InDesign version 16.x is found, verify if the installed version falls between 16.0 and 16.4.2 inclusive. Any version 16.0 through 16.4.2 is within the affected range.
    Affected if Installed version is 16.0, 16.1, 16.2, 16.3, 16.4, 16.4.1, or 16.4.2
  3. Compare version against affected 17.x range
    If InDesign version 17.x is found, verify if the installed version falls between 17.0 and 17.3 inclusive. Any version 17.0 through 17.3 is within the affected range.
    Affected if Installed version is 17.0, 17.1, 17.2, or 17.3
  4. Check for automatic file handling from untrusted sources
    Review InDesign preferences and file association settings to determine if the application is configured to automatically open files from external or untrusted locations.
    Affected if Application automatically opens files without user confirmation (increases exposure to malicious files)

The environment is affected if Adobe InDesign installed version is 16.0 through 16.4.2 or 17.0 through 17.3, regardless of operating system platform.

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 patched versions (16.4.3+ for desktop, 17.4+ for subscription) and exercise caution when opening files from untrusted sources.

Recommended fix High confidence

InDesign 16.4.3+ or 17.4+ (depending on your major version branch)

  1. 1. Close Adobe InDesign if it is currently running
  2. 2. For InDesign version 16.x users: Upgrade to InDesign version 16.4.3 or later
  3. 3. For InDesign version 17.x users: Upgrade to InDesign version 17.4 or later
  4. 4. After upgrading, verify the installed version matches or exceeds the fixed release
  5. 5. Do not open untrusted or unsolicited InDesign files from unknown sources
Caveat Minor version upgrades within the same major branch typically preserve settings and workflows; verify compatibility with custom scripts or plugins after upgrading

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

Fix this in Fedora Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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