IllustratorApplication · Adobe

CVE-2024-34137

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 27.9.5 / 28.6 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
Illustrator versions 28.5, 27.9.4 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 · moderate confidence

Adobe Illustrator versions 28.5 and earlier contain a NULL Pointer Dereference vulnerability where processing a specially crafted malicious file causes the application to attempt dereferencing an uninitialized or null pointer, resulting in a crash and denial-of-service condition.

MitigationApply Adobe's security patch for Illustrator when available; avoid opening files from untrusted or unknown sources.

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
IllustratorApplication
Affected:>= 27.0.0, < 27.9.5>= 28.0, < 28.6

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. Identify installed Adobe Illustrator version
    Open Illustrator, go to Help > About Illustrator, or check Add/Remove Programs (Windows) / Applications folder (macOS) for the installed version
    Affected if Version is 27.0.0 through 27.9.5, or 28.0 through 28.5 (or 28.5.x)
  2. Confirm version is within affected ranges
    Compare your installed version number against the vulnerable ranges: 27.0.0 <= version < 27.9.5 OR 28.0 <= version < 28.6
    Affected if Installed version falls within either 27.0.0 to 27.9.5 or 28.0 to 28.5 (versions prior to 27.9.5 or prior to 28.6)
  3. Note trigger condition
    This vulnerability is triggered when processing a specially crafted malicious file - no special configuration or feature needs to be enabled for the flaw to exist in the code
    Affected if The vulnerable version is installed and the application processes files (normal operation exposes the attack surface)

You are affected if Adobe Illustrator version 27.0.0 through 27.9.5 or version 28.0 through 28.5 is installed on your system.

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 27.9.5 / 28.6 or later
Fixed in 27.9.528.6
Interim mitigation

Apply Adobe's security patch for Illustrator when available; avoid opening files from untrusted or unknown sources.

Recommended fix High confidence

Upgrade to Illustrator version 27.9.5 or later for the 27.x release line, or version 28.6 or later for the 28.x release line

  1. Close Adobe Illustrator if it is currently running
  2. Open the Adobe Creative Cloud desktop application
  3. Navigate to the 'Apps' or 'All Apps' section
  4. Locate Adobe Illustrator in the list of installed applications
  5. Click the 'Update' button next to Adobe Illustrator to install the latest available version
  6. Alternatively, for specific version control, uninstall the current version and reinstall using an installer for version 27.9.5 or 28.6 or later from Adobe's official downloads
  7. Restart the computer after the update completes
  8. Launch Illustrator and verify the application runs without crashes
Caveat Patch releases typically include backward-compatible fixes; review Adobe's release notes for any specific functionality changes

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

Fix this in Illustrator Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

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