CVE-2024-34127
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 · uneditedInDesign Desktop versions ID19.4, ID18.5.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 · moderate confidenceAdobe InDesign Desktop versions ID19.4, ID18.5.2 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. This memory disclosure can be leveraged by attackers to bypass ASLR (Address Space Layout Randomization) security mitigations. Exploitation requires user interaction—specifically, a victim must open a maliciously crafted 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< 18.5.3>= 19.0, < 19.5CVSS 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.
-
Locate installed Adobe InDesign versionOpen Adobe InDesign, then go to Help > About InDesign. The version number will display in the dialog. Alternatively, on Windows check Programs and Features in Control Panel; on macOS check Applications folder or System Settings > General > About > Applications.Affected if Version cannot be determined or application is not installed - cannot assess vulnerability status
-
Identify the major version numberNote whether the installed version begins with 18.x or 19.x (the first two digits before the decimal indicate the major release).Affected if Version does not start with 18 or 19 - not in scope for this CVE
-
Compare version against affected rangesIf version starts with 18: check if it is earlier than 18.5.3 (versions like 18.5.2, 18.5.1, 18.5, 18.4.x, etc.). If version starts with 19: check if it is 19.0 through 19.4.x (any version before 19.5).Affected if Version is 18.x before 18.5.3 OR version is 19.0 through 19.4.x - environment is vulnerable
Your environment is affected if Adobe InDesign is installed and the version is either 18.x earlier than 18.5.3 or 19.x earlier than 19.5.
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 · scoped18.5.319.5
Organizations should update InDesign to the latest patched version. Users should avoid opening files from untrusted or unknown sources until the patch is applied.
InDesign 18.5.3+ or 19.5+ depending on your major version line
- 1. Close any running instances of Adobe InDesign
- 2. Back up your current InDesign projects and settings
- 3. Navigate to the Adobe Creative Cloud desktop application or visit helpx.adobe.com
- 4. Check for available updates for Adobe InDesign
- 5. For InDesign versions below 18.5.3: upgrade to version 18.5.3 or later
- 6. For InDesign versions 19.0 through 19.4: upgrade to version 19.5 or later
- 7. After installation, verify the version by opening InDesign and checking Help > About InDesign
- 8. Do not open untrusted or unexpected InDesign files from unknown sources
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34127 — 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-2024-34127 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