CVE-2022-28855
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 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 confidenceAdobe InDesign versions 16.4.2 and earlier (16.x) and 17.3 and earlier (17.x) contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. This information disclosure can be leveraged to defeat Address Space Layout Randomization (ASLR) as a secondary attack step. Exploitation requires user interaction—the victim must open a maliciously crafted InDesign file.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed InDesign version on WindowsOpen the Windows Control Panel, go to Programs and Features, locate Adobe InDesign in the list, and note the version number shown in the Version column. Alternatively, launch InDesign, go to Help > About InDesign to view the exact version and build number.Affected if The version is 16.4.2 or earlier in the 16.x series, or 17.3 or earlier in the 17.x series.
-
Check installed InDesign version on macOSOpen Finder, navigate to the Applications folder, right-click on Adobe InDesign, select Get Info, and read the Version field. You can also open InDesign and go to InDesign > About InDesign to see the full version and build details.Affected if The version is 16.4.2 or earlier in the 16.x series, or 17.3 or earlier in the 17.x series.
-
Verify the specific InDesign release channelAdobe InDesign ships in two release channels: 16.x (2021 and earlier) and 17.x (2022 and later). Check which major version number your installation uses, as both channels contain separate vulnerable version ranges.Affected if You are running version 16.0 through 16.4.2, or version 17.0 through 17.3.
-
Confirm whether untrusted files have been openedReview recent InDesign file open events. Check if any .indd or .idml files from untrusted or unknown sources have been opened recently, as exploitation requires user interaction with a maliciously crafted file.Affected if A suspicious or untrusted InDesign document was opened on a system with a vulnerable version.
You are affected if Adobe InDesign version 16.0 through 16.4.2 or version 17.0 through 17.3 is installed, and a user opened a maliciously crafted InDesign file.
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 · scopedUpdate Adobe InDesign to the latest patched version beyond 16.4.2 and 17.3. Avoid opening untrusted or unsolicited InDesign files from unknown sources.
InDesign 16.5 or later; InDesign 17.4 or later
- 1. Close Adobe InDesign if it is currently running
- 2. Open Adobe Creative Cloud desktop application or navigate to Adobe's official download page
- 3. Locate Adobe InDesign in your installed applications
- 4. Check for available updates or navigate to the InDesign product page
- 5. Download and install the latest version of Adobe InDesign
- 6. Alternatively, navigate to helpx.adobe.com and search for the InDesign security update bulletin for this CVE
- 7. Download the patched version from Adobe's official sources
- 8. Verify the installed version matches or exceeds 16.5 (for 16.x users) or 17.4 (for 17.x users)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28855 — 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-28855 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