CVE-2024-47438
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 Write-what-where Condition vulnerability that could lead to a memory leak. This vulnerability allows an attacker to write a controlled value at a controlled memory location, which could result in the disclosure of sensitive memory content. 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 confidenceA write-what-where condition vulnerability in Adobe Substance3D Painter versions 10.1.0 and earlier allows an attacker to write controlled values at arbitrary memory locations by convincing a user to open a malicious file. This can lead to memory disclosure and potentially sensitive data exposure.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe Substance 3D Painter versionOpen the application, then go to Help > About Adobe Substance 3D Painter. The version number is displayed in the dialog that opens.Affected if The displayed version is 10.1.0 or earlier (any version below 10.1.1)
-
Confirm version via application executableLocate the Substance 3D Painter executable (commonly in C:\Program Files\Adobe\Adobe Substance 3D Painter on Windows or /Applications/Adobe Substance 3D Painter on macOS), right-click it, select Properties, and view the File Version or Product Version information.Affected if The version shown is less than 10.1.1
-
Check for recently opened image filesReview the application's recent files list (File > Recent Files) or check the system file explorer for recently modified .tga, .png, or other image files that may have been opened in the application.Affected if Untrusted or suspicious image files were opened in the application, especially from unknown sources
-
Audit file handling environmentExamine the directory where image files are typically loaded from, looking for any unexpected or unsolicited image files that may have been received from untrusted sources.Affected if The application has processed image files from untrusted or suspicious sources since the vulnerability exists
A user is affected if Adobe Substance 3D Painter version 10.1.0 or earlier is installed AND the system has opened untrusted image files, as the malicious file handling is the trigger for this write-what-where vulnerability.
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
Apply the vendor security update from Adobe when available; until then, exercise caution with untrusted .tga, .png, or image files and consider restricting file handling permissions.
Substance 3D Painter 10.1.1
- Verify current Adobe Substance 3D Painter version by opening the application and checking Help > About
- Navigate to the official Adobe download page at helpx.adobe.com or the Adobe Creative Cloud desktop application
- Download Substance 3D Painter version 10.1.1 or later
- Close any running instances of Adobe Substance 3D Painter
- Run the installer and follow the on-screen prompts to complete the upgrade
- Launch the updated application and confirm the version shows 10.1.1 or higher under Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47438 — 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-47438 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