dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2024-39388

HIGH · 7.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 3.0.3 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
Substance3D - Stager versions 3.0.2 and earlier are affected by a Use After Free 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

A Use After Free vulnerability in Substance3D Stager versions 3.0.2 and earlier allows arbitrary code execution when parsing malicious files. The vulnerability occurs because the application continues to use memory after it has been freed, which an attacker can exploit to run arbitrary code in the context of the current user.

MitigationUpdate Substance3D Stager to a version newer than 3.0.2. Avoid opening files from untrusted sources until the patch is applied.

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
Substance 3d StagerApplication
Affected:< 3.0.3

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. Locate installed Adobe Substance 3D Stager version
    Open the application, then go to Help > About Adobe Substance 3D Stager (or check the version in the application launcher/installed programs list on Windows via Programs and Features, or macOS via Applications folder Get Info)
    Affected if The displayed version is 3.0.2 or earlier (versions below 3.0.3 are affected)
  2. Verify Windows installation path and file version
    On Windows, navigate to the installation directory (typically C:\Program Files\Adobe\Adobe Substance 3D Stager) and locate the main executable (e.g., Substance 3D Stager.exe). Right-click the executable, select Properties, and check the File Version on the Details tab
    Affected if The file version shown is prior to 3.0.3
  3. Verify macOS installation package version
    On macOS, open Finder, go to Applications, right-click Adobe Substance 3D Stager, select Get Info, and check the version under General
    Affected if The version listed is 3.0.2 or earlier (versions below 3.0.3 are vulnerable)

If Adobe Substance 3D Stager is installed and the version is 3.0.2 or earlier (anything below 3.0.3), the environment is affected by this Use After Free vulnerability when parsing potentially malicious 3D files.

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

Update Substance3D Stager to a version newer than 3.0.2. Avoid opening files from untrusted sources until the patch is applied.

Recommended fix High confidence

Substance 3D Stager 3.0.3 or later

  1. Open Adobe Creative Cloud desktop application or navigate to the Substance 3D Stager product page
  2. Check the current installed version of Substance 3D Stager (Help > About in the application)
  3. If version is 3.0.2 or earlier, initiate the update to version 3.0.3
  4. Alternatively, download Substance 3D Stager version 3.0.3 or later directly from Adobe's official website at helpx.adobe.com
  5. Install the updated version, ensuring to close the application if currently running
  6. Verify the installed version shows 3.0.3 or later after installation completes

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

Fix this in Substance 3d Stager 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-39388 — 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-39388 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