dbcve.org
DimensionApplication · Adobe

CVE-2024-34126

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to after 3.4.11 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
Dimension versions 3.4.11 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 Dimension versions 3.4.11 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. This information leak can be leveraged to defeat ASLR (Address Space Layout Randomization) as a secondary attack vector. Successful exploitation requires a victim to open a specially crafted malicious file.

MitigationUpdate Adobe Dimension to version 3.4.12 or later. Avoid opening files from untrusted sources as exploitation requires user interaction.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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. Confirm Adobe Dimension is installed
    Check for the presence of Adobe Dimension on the system. On Windows, look in C:\Program Files\Adobe\Adobe Dimension or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Adobe Dimension.exe. On macOS, check /Applications/Adobe Dimension.app.
    Affected if Adobe Dimension is not installed on the system.
  2. Determine the installed version number
    Right-click on Adobe Dimension.exe (Windows) or Get Info on Adobe Dimension.app (macOS), or run the executable with a version flag if available. On Windows, you can also check the file version property of the main executable.
    Affected if The exact version cannot be determined.
  3. Compare version against affected range
    Compare the installed version to the affected range: versions 3.4.11 and earlier are vulnerable. Version 3.4.12 or later contains the fix.
    Affected if The installed version is 3.4.11 or earlier.
  4. Verify the executable file version
    On Windows, right-click the Adobe Dimension executable, select Properties, and check the File Version field. On macOS, right-click Adobe Dimension.app, select Show Package Contents, and check Info.plist for CFBundleShortVersionString.
    Affected if The file version shows 3.4.11 or earlier.

The user is affected if Adobe Dimension is installed and the installed version is 3.4.11 or earlier; version 3.4.12 or later is not affected.

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

Update Adobe Dimension to version 3.4.12 or later. Avoid opening files from untrusted sources as exploitation requires user interaction.

Recommended fix Moderate confidence

Dimension 3.4.12 or later

  1. Open Adobe Creative Cloud desktop application or check for updates within Adobe Dimension
  2. Navigate to the updates section and look for Dimension update
  3. Update Adobe Dimension to the latest available version (version 3.4.12 or later)
  4. Alternatively, download the latest version from the Adobe website and reinstall

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

Fix this in Dimension Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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