dbcve.org
IncopyApplication · Adobe

CVE-2024-45136

HIGH · 7.8 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 18.5.4 / 19.5 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
InCopy versions 19.4, 18.5.3 and earlier are affected by an Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitrary code execution by an attacker. An attacker could exploit this vulnerability by uploading a malicious file which can then be executed on the server. Exploitation of this issue requires user interaction.

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

This is an unrestricted file upload vulnerability (CWE-434) in Adobe InCopy versions 19.4, 18.5.3 and earlier that allows attackers to upload malicious files capable of arbitrary code execution. The vulnerability requires user interaction, likely meaning a user must open or process a specially crafted file within the application.

MitigationApply the vendor patch by updating InCopy to a version beyond 19.4 and 18.5.3; restrict file upload capabilities and validate all file types before processing to mitigate the attack vector.

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
IncopyApplication
Affected:< 18.5.4>= 19.0, < 19.5

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 InCopy is installed
    Check for InCopy in the installed applications - on Windows check Program Files/Adobe folder or Add/Remove Programs; on macOS check /Applications/Adobe InCopy or Launchpad
    Affected if Adobe InCopy is present on the system
  2. Determine installed InCopy version
    Open InCopy, go to Help > About InCopy (or InCopy > About InCopy on macOS) to view the exact version number, or check the Windows Registry at HKLM\SOFTWARE\Adobe\InCopy\Version or macOS plist files
    Affected if Version displays as 18.5.3 or earlier, or 19.0 through 19.4
  3. Compare version against affected ranges
    Review the version number against these vulnerable ranges: versions before 18.5.4, and versions 19.0 through 19.5
    Affected if Installed version is < 18.5.4 OR (>= 19.0 AND < 19.5)
  4. Identify file import sources
    Review workflow for InCopy - determine if the application is used to open or import files from external, untrusted, or internet-based sources
    Affected if Users routinely open .icml, .incx, or other InCopy files from untrusted or unknown sources

User is affected if Adobe InCopy is installed with a version number in the ranges < 18.5.4 or >= 19.0 to < 19.5 AND the application is used to process files from external or untrusted sources.

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.4 / 19.5 or later
Fixed in 18.5.419.5
Interim mitigation

Apply the vendor patch by updating InCopy to a version beyond 19.4 and 18.5.3; restrict file upload capabilities and validate all file types before processing to mitigate the attack vector.

Recommended fix High confidence

InCopy 18.5.4 or InCopy 19.5 (depending on your major version branch)

  1. 1. Close Adobe InCopy if it is currently running
  2. 2. Open Adobe Creative Cloud desktop application or navigate to adobe.com/downloads
  3. 3. Locate Adobe InCopy in your installed applications
  4. 4. Check the current version by opening InCopy and going to Help > About InCopy
  5. 5. Initiate the update to version 18.5.4 (for versions 18.x) or version 19.5 (for versions 19.x)
  6. 6. Wait for the update to download and install completely
  7. 7. Restart InCopy and verify the version shows 18.5.4 or 19.5
  8. 8. Test that file upload/import functionality works as expected
Caveat Standard Adobe update; minor version bump with focus on security fix - no expected breaking changes for typical workflows

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

Fix this in Incopy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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