CVE-2024-47439
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 - Painter versions 10.1.0 and earlier are affected by a NULL Pointer Dereference vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. 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 confidenceAdobe Substance3D Painter versions 10.1.0 and earlier contain a NULL Pointer Dereference vulnerability that can be triggered when a user opens a maliciously crafted file. The vulnerability causes the application to crash due to dereferencing a null pointer, resulting in denial-of-service.
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< 10.1.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Confirm Adobe Substance 3D Painter is installedLocate the application on the system. On Windows, check C:\Program Files\Adobe\Adobe Substance 3D Painter or search for the executable. On macOS, check /Applications/Adobe Substance 3D Painter or use Spotlight to search for the application.Affected if The application is present on the system
-
Identify the installed version numberLaunch Adobe Substance 3D Painter and navigate to Help > About Adobe Substance 3D Painter to display the version information, or right-click the application in the system registry or application folder to view version details. Compare the version to 10.1.1.Affected if The installed version is 10.1.0 or any earlier version (versions lower than 10.1.1)
-
Determine if users open external files in the applicationAssess whether users of Substance 3D Painter commonly open files from external or untrusted sources, as the vulnerability is triggered when a maliciously crafted file is opened.Affected if Users open files from untrusted or unverified sources in the application, which would trigger the vulnerability
The environment is affected if Adobe Substance 3D Painter version 10.1.0 or earlier is installed and users open external files in the application, as the null pointer dereference occurs when a crafted file is opened.
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 · scoped10.1.1
Users should avoid opening untrusted or unverified files in Substance3D Painter until Adobe releases an official patch addressing this vulnerability.
10.1.1
- Verify current version of Adobe Substance 3D Painter by opening the application and checking Help > About
- Download Adobe Substance 3D Painter version 10.1.1 or later from the official Adobe website (helpx.adobe.com)
- Close any running instances of Adobe Substance 3D Painter
- Install the downloaded update by following the on-screen installation prompts
- Restart Adobe Substance 3D Painter after installation completes
- Confirm the installed version is 10.1.1 or later via Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47439 — 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-47439 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