IndesignApplication · Adobe

CVE-2024-41836

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-23
Fix available
A fix is available. Upgrade to 18.5.3 / 19.4 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
InDesign Desktop versions ID18.5.2, ID19.3 and earlier are affected by a NULL Pointer Dereference vulnerability that could lead to an application denial-of-service (DoS) condition. An attacker could exploit this vulnerability to crash the application, resulting in a DoS. 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 confidence

A NULL pointer dereference vulnerability in Adobe InDesign Desktop versions ID18.5.2, ID19.3 and earlier allows attackers to crash the application and cause denial of service by enticing users to open specially crafted malicious files.

MitigationApply the vendor patch when released and advise users to avoid opening untrusted InDesign files until the update is applied.

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
IndesignApplication
Affected:< 18.5.3>= 19.0, < 19.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate installed Adobe InDesign version
    Open Adobe Creative Cloud desktop app, navigate to the Apps tab, and find InDesign in the installed software list. Alternatively, open InDesign and go to Help > About Adobe InDesign to see the full version number.
    Affected if Version displayed is below 18.5.3 or falls between 19.0 and 19.4 inclusive
  2. Confirm InDesign installation via command line
    Windows: Check C:\Program Files\Adobe\Adobe InDesign [version] folder exists. Mac: Check /Applications/Adobe InDesign [version] exists. Use 'dir' or 'ls' to list installed Adobe applications.
    Affected if An Adobe InDesign installation folder exists with a version subfolder matching vulnerable version numbers
  3. Verify version number format against advisory
    Compare your installed version number (such as 18.5.2, 19.0, 19.3, or 19.4) against the affected ranges: versions lower than 18.5.3, or versions 19.0 through 19.4
    Affected if Installed version falls within < 18.5.3 or >= 19.0 and < 19.4

You are affected if Adobe InDesign Desktop is installed and the version number is either below 18.5.3 or between 19.0 and 19.4 inclusive, since the vulnerability triggers when opening maliciously crafted files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 18.5.3 / 19.4 or later
Fixed in 18.5.319.4
Interim mitigation

Apply the vendor patch when released and advise users to avoid opening untrusted InDesign files until the update is applied.

Recommended fix High confidence

InDesign 18.5.3 or later for 18.x branch; InDesign 19.4 or later for 19.x branch

  1. Check current InDesign version by opening the application and going to Help > About InDesign
  2. If running version 18.x (e.g., 18.5.2 or earlier), upgrade to InDesign version 18.5.3 or later
  3. If running version 19.0 through 19.3, upgrade to InDesign version 19.4 or later
  4. Download the updated version from the official Adobe website (helpx.adobe.com) or through Adobe Creative Cloud desktop application
  5. Restart the application after installation
Caveat Standard minor version upgrades typically include bug fixes without significant behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Indesign Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41836 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41836 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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