CVE-2023-47077
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 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 confidenceThis is an out-of-bounds read vulnerability in Adobe InDesign versions 19.0 and earlier and 17.4.2 and earlier. The flaw allows reading sensitive memory contents beyond allocated boundaries, which can expose application memory data. Attackers can exploit this by crafting malicious files that, when opened by victims, leak memory information. The disclosed memory contents can potentially reveal pointers or addresses that enable attackers to bypass ASLR protection mechanisms.
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
- 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 if Adobe InDesign is installedLocate the Adobe InDesign application in the system (typically in Program Files on Windows or Applications folder on macOS). The application executable is commonly named InDesign.exe (Windows) or InDesign.app (macOS).Affected if If Adobe InDesign is present on the system, proceed to version check.
-
Determine installed InDesign versionOpen Adobe InDesign and navigate to Help > About InDesign (Windows) or InDesign > About InDesign (macOS). Alternatively, check the Windows Registry under HKLM\SOFTWARE\Adobe\InDesign\InstallPath or examine the application info.plist on macOS.Affected if The exact version number displayed must be captured for comparison.
-
Compare version against affected rangesCheck if the installed version falls within: 17.0 through 17.4.2 (inclusive), OR exactly version 19.0. These are the vulnerable versions per the CVE.Affected if If the installed version is 17.0, 17.1, 17.2, 17.3, 17.4, 17.4.1, 17.4.2, or 19.0, the environment is affected by this vulnerability.
-
Verify file handling is the attack vectorThis vulnerability is triggered when a user opens a specially crafted malicious file in InDesign. No specific configuration toggle enables or disables this; it is a built-in file parsing operation.Affected if If a vulnerable version is confirmed and the application is used to open files from untrusted sources, exploitation is possible.
If Adobe InDesign version is 17.0 through 17.4.2 or exactly 19.0, the environment is vulnerable to out-of-bounds memory reading via malicious file handling.
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 the latest patched version as provided by Adobe's security advisory. Additionally, enforce user awareness about not opening untrusted or unsolicited files, as exploitation requires victim interaction to open a malicious file.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47077 — 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-47077 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