CVE-2023-47076
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 19.0 (and earlier) and 17.4.2 (and earlier) are affected by a NULL Pointer Dereference vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve an application denial-of-service 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 19.0 and earlier, and 17.4.2 and earlier contain a NULL Pointer Dereference vulnerability in the file parsing logic. When a user opens a specially crafted malicious file, the application attempts to dereference a NULL pointer, causing a crash and resulting in denial-of-service conditions.
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>= 17.0, <= 17.4.2= 19.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Determine installed Adobe InDesign versionOpen Adobe InDesign, then go to Help > About Adobe InDesign (Windows) or InDesign > About InDesign (Mac). The version number displays in the window title or about dialog.Affected if Version displayed is 19.0 or falls within 17.0 through 17.4.2 inclusive
-
Verify version via application executableLocate the InDesign executable (ID.exe on Windows, InDesign on Mac) in the installation directory. Right-click and view Properties, or use command line tools to query version information.Affected if The executable version property matches 19.0 or any version from 17.0 to 17.4.2
-
Check product version via system installed programs listOn Windows, open Programs and Features from Control Panel. On macOS, open Applications folder and view Get Info on the InDesign app. Note the full version number listed.Affected if Listed version is 19.0 or ranges from 17.0 to 17.4.2
You are affected if Adobe InDesign installed on this system is version 19.0 or any version from 17.0 through 17.4.2, as these versions contain the NULL pointer dereference flaw 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 · scopedUpdate Adobe InDesign to the latest patched version provided by Adobe. Users should avoid opening untrusted or unexpected InDesign files from unverified sources.
Adobe InDesign 17.4.3 or later (for 17.x line); Adobe InDesign 19.1 or later (for 19.x line)
- 1. Verify current Adobe InDesign version by opening the application and navigating to Help > About Adobe InDesign
- 2. If running version 17.0 through 17.4.2, download and install version 17.4.3 or later from the official Adobe website
- 3. If running version 19.0 (or earlier), download and install version 19.1 or later from the official Adobe website
- 4. After installation, verify the updated version by checking Help > About Adobe InDesign
- 5. Test that existing workflows function normally with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47076 — 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-2023-47076 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