dbcve.org
IllustratorApplication · Adobe

CVE-2024-45114

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 28.7.2 or later.
See remediation →
81/100
Remediation priority · High
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.7.1 and earlier are affected by an out-of-bounds write vulnerability that could result in arbitrary code execution 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 confidence

Adobe Illustrator versions 28.7.1 and earlier contain an out-of-bounds write vulnerability during file parsing. An attacker can craft a malicious file that, when opened by a victim, triggers memory corruption leading to arbitrary code execution in the current user's context.

MitigationUpdate Adobe Illustrator to version 28.7.2 or later. Until patched, do not open .ai files or other supported file formats from untrusted 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:< 28.7.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Verify Adobe Illustrator is installed
    Check for Adobe Illustrator installation: On Windows, look in C:\Program Files\Adobe\Adobe Illustrator [Version] or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* for Adobe Illustrator entry. On macOS, check /Applications/Adobe Illustrator [Version].
    Affected if Adobe Illustrator is present on the system
  2. Get installed version number
    On Windows: Open Adobe Illustrator, go to Help > About Adobe Illustrator. Or run: reg query 'HKLM\SOFTWARE\Adobe\Adobe Illustrator' /v Version (path varies by version). On macOS: Right-click Adobe Illustrator in Applications, select Get Info, check Version.
    Affected if Unable to determine version or version is below 28.7.2
  3. Compare version against affected range
    Compare the installed version to the affected range: versions 28.7.1 and earlier are vulnerable. Version 28.7.2 and later are patched.
    Affected if Installed version is 28.7.1 or earlier, or any version less than 28.7.2
  4. Confirm file parsing is accessible
    The vulnerability triggers when opening .ai files or other supported formats. If Adobe Illustrator is installed and can open files, the file parsing module is available.
    Affected if Adobe Illustrator can open files - the parsing module is enabled by default in normal installations
  5. Identify recent .ai file activity (optional)
    Check for recently opened .ai files: On Windows, review JumpList recent items or search for .ai files in recent documents. On macOS, check ~/Library/Application Support/Adobe/Adobe Illustrator recent files.
    Affected if Suspicious or untrusted .ai files were recently opened - indicates potential exposure vector

User is affected if Adobe Illustrator version 28.7.1 or earlier is installed and the application can parse files, which is the default state when Illustrator is installed.

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 28.7.2 or later
Fixed in 28.7.2
Interim mitigation

Update Adobe Illustrator to version 28.7.2 or later. Until patched, do not open .ai files or other supported file formats from untrusted sources.

Recommended fix High confidence

28.7.2

  1. Open Adobe Creative Cloud desktop application
  2. Navigate to the 'Apps' section
  3. Find Adobe Illustrator in the list of installed apps
  4. Click the 'Update' button next to Adobe Illustrator
  5. Wait for the update to download and install version 28.7.2
  6. Restart Illustrator if prompted
  7. Verify the installed version by going to Help > About Adobe Illustrator and confirming it shows version 28.7.2

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

Fix this in Illustrator Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-45114 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