CVE-2022-28852
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 16.4.2 (and earlier) and 17.3 (and earlier) are affected by 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 contains an out-of-bounds write vulnerability in the file parsing logic that allows arbitrary code execution when processing a maliciously crafted INDD file. The vulnerability stems from improper bounds checking during file parsing, leading to memory corruption that can be leveraged for code execution in the context of the current user.
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.0, <= 16.4.2>= 17.0, <= 17.3CVSS 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.
-
Confirm InDesign installationLocate Adobe InDesign on the system - on Windows check Program Files/Adobe folder or Programs and Features list, on macOS check the Applications folderAffected if InDesign is present on the system
-
Identify installed InDesign versionLaunch InDesign and navigate to Help > About InDesign (Windows) or InDesign > About InDesign (macOS), or check the version in system installed programs detailsAffected if Version number cannot be determined from the application or system
-
Compare version to affected rangesMatch the installed version against CVE ranges: version 16.0 through 16.4.2 inclusive, or version 17.0 through 17.3 inclusiveAffected if Installed version falls within either 16.0-16.4.2 or 17.0-17.3
User is affected if Adobe InDesign is installed with a version number between 16.0 and 16.4.2, or between 17.0 and 17.3, as these ranges contain the vulnerability in file parsing logic.
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.
dbcve · scopedApply vendor-supplied security updates (InDesign 16.4.3 and 17.4 or later) to address the vulnerability. Until patched, avoid opening InDesign files from untrusted or unknown sources.
Adobe InDesign 16.4.3 (for 16.x line) or Adobe InDesign 17.4 (for 17.x line)
- Open Adobe InDesign and check the current version via Help > About InDesign
- If version is 16.0 through 16.4.2, download and install Adobe InDesign version 16.4.3 or later from adobe.com
- If version is 17.0 through 17.3, download and install Adobe InDesign version 17.4 or later from adobe.com
- Verify successful installation by checking Help > About InDesign shows the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28852 — 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-28852 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