CVE-2024-45142
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 · uneditedSubstance3D - Stager versions 3.0.3 and earlier are affected by a Write-what-where Condition vulnerability that could allow an attacker to execute arbitrary code in the context of the current user. This vulnerability allows an attacker to write a controlled value to an arbitrary memory location, potentially leading to code execution. 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 confidenceAdobe Substance3D Stager versions 3.0.3 and earlier contain a write-what-where vulnerability that allows a maliciously crafted file to write controlled values to arbitrary memory locations, leading to arbitrary code execution in the context of the current user. Exploitation requires user interaction to open a specially crafted file.
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< 3.0.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe Substance 3D Stager versionLocate the Adobe Substance 3D Stager application on your system and retrieve its version information (typically found in the application's properties, about dialog, or installer information)Affected if The installed version is 3.0.3 or earlier, or any version prior to 3.0.4
-
Confirm the specific version numberCompare your identified version against the affected range: any version lower than 3.0.4 is vulnerableAffected if Version is less than 3.0.4 (for example, 3.0.3, 3.0.2, 3.0.1, 3.0.0, or earlier)
-
Determine if .stg files are processedVerify whether the Stager application is used to open or handle .stg scene files in your environmentAffected if Users routinely open .stg files with this software, as exploitation requires opening a specially crafted file
You are affected if Adobe Substance 3D Stager version is lower than 3.0.4 and users open .stg files with it.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.0.4
Apply available vendor patches for Substance3D Stager; until patched, warn users against opening .stg or related files from untrusted sources.
Substance 3D Stager 3.0.4
- Navigate to Adobe's official support website (helpx.adobe.com) or the Substance 3D Stager product page
- Locate and download the latest version of Substance 3D Stager (version 3.0.4 or later)
- Install the update following Adobe's standard installation process
- Restart the application if prompted
- Verify the installed version is 3.0.4 or later by checking the application's 'About' or version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,064.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45142 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45142 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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