DimensionApplication · Adobe

CVE-2024-41865

HIGH · 7.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to after 3.4.11 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
Dimension versions 3.4.11 and earlier are affected by an Untrusted Search Path vulnerability that could lead to arbitrary code execution. An attacker could exploit this vulnerability by inserting a malicious file into the search path, which the application might execute instead of the legitimate file. This could occur if the application uses a search path to locate executables or libraries. 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 · moderate confidence

Dimension versions 3.4.11 and earlier contain an Untrusted Search Path vulnerability where the application uses a search path to locate executables or libraries without proper validation. An attacker can place a malicious file in a directory within this search path (such as the current working directory) that gets executed in place of the legitimate file, leading to arbitrary code execution. User interaction is required for exploitation.

MitigationHardcode absolute paths for all executables and libraries, remove the current directory (.) from PATH and search paths, or implement validation to ensure only trusted directories are searched. Verify that no user-writable directories appear in the application's search path.

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
DimensionApplication
Affected:<= 3.4.11

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. Check Adobe Dimension installed version
    Open Adobe Dimension, go to Help > About Adobe Dimension, or check Programs and Features in Control Panel for the version number
    Affected if Version is 3.4.11 or earlier
  2. Inspect system PATH environment variable
    Open Command Prompt and run 'echo %PATH%' to view all directories in the system PATH
    Affected if Current directory (.) or user-writable directories appear in PATH before system directories
  3. Check Adobe Dimension executable location
    Locate the Dimension executable (Dimension.exe) by right-clicking the desktop shortcut, selecting Properties, and examining the 'Start in' field or executable path
    Affected if The application is launched from or points to a user-writable directory like the desktop or downloads folder
  4. Monitor DLL/library search behavior
    Use Process Monitor (Sysinternals) to trace DLL/library loads by Dimension.exe, filtering for NAME NOT STARTING WITH C:\Windows
    Affected if Dimension loads any DLL or library from current working directory or user-writable locations outside Program Files

You are affected if Adobe Dimension version is 3.4.11 or earlier AND the application searches for executables/libraries in directories that include the current working directory or other user-writable locations.

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 a release after 3.4.11
Interim mitigation

Hardcode absolute paths for all executables and libraries, remove the current directory (.) from PATH and search paths, or implement validation to ensure only trusted directories are searched. Verify that no user-writable directories appear in the application's search path.

Recommended fix Moderate confidence

Latest available Adobe Dimension version (beyond 3.4.11)

  1. Open Adobe Creative Cloud desktop application or visit the Adobe Dimension download page
  2. Navigate to the updates or downloads section for Adobe Dimension
  3. Download and install the latest available version of Adobe Dimension
  4. Verify the installed version by opening Dimension and checking Help > About Adobe Dimension
  5. Restart any running instances of the application to ensure the update takes effect
Caveat Ensure system meets minimum requirements for the new version; review Adobe's release notes for any feature changes

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

Fix this in Dimension Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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