dbcve.org
Substance 3d StagerApplication · Adobe

CVE-2024-45143

HIGH · 7.8 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 3.0.4 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.3 and earlier are affected by a Heap-based Buffer Overflow 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 · moderate confidence

A heap-based buffer overflow vulnerability exists in Substance3D Stager versions 3.0.3 and earlier. The flaw can be triggered when a user opens a specially crafted malicious file, allowing arbitrary code execution with the privileges of the current user.

MitigationApply the vendor patch by upgrading to a version newer than 3.0.3 when available, and instruct users to avoid opening untrusted or unsolicited files in Substance3D Stager until the update is deployed.

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.4

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 if Adobe Substance 3D Stager is installed
    On Windows, check Program Files for 'Adobe Substance 3D Stager' folder, or look in the list of installed applications in Settings > Apps. On macOS, check /Applications folder for 'Substance 3D Stager.app'
    Affected if The software is present on the system
  2. Determine the installed version of Substance 3D Stager
    On Windows, open the app, go to Help > About or check the version in the application's properties. On macOS, right-click the app in Finder, select Get Info, and view the version number. Alternatively, check the version in the Windows Registry under HKLM\SOFTWARE\Adobe\Substance3DStager
    Affected if A version number is found that is 3.0.3 or earlier, or any version below 3.0.4
  3. Verify the vulnerable file parsing component is present
    The vulnerability is in the core file handling - confirm the application's file import functionality is available by attempting to use File > Open or checking that common 3D file formats (.sbsar, .sbs, .fbx, .obj) can be loaded
    Affected if The application can open or import 3D files, which enables the attack vector
  4. Confirm the specific vulnerable condition
    No special configuration check needed - the vulnerability triggers when a user opens a specially crafted malicious file through the application's standard file open dialog
    Affected if The user has the ability to open files within the application, which is the default state for this software

You are affected if Adobe Substance 3D Stager is installed and the version is 3.0.3 or any version lower than 3.0.4.

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

Apply the vendor patch by upgrading to a version newer than 3.0.3 when available, and instruct users to avoid opening untrusted or unsolicited files in Substance3D Stager until the update is deployed.

Recommended fix High confidence

3.0.4

  1. Check the current version of Adobe Substance 3D Stager by opening the application and navigating to Help > About (or checking in the application menu)
  2. Visit the official Adobe website or helpx.adobe.com to download Substance 3D Stager version 3.0.4 or later
  3. Run the downloaded installer and follow the on-screen prompts to update the application
  4. Restart the application if prompted or manually close and reopen it
  5. Verify the installation was successful by checking the version number again (should show 3.0.4 or higher)

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

Fix this in Substance 3d Stager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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