CVE-2024-47435
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 an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 confidenceAn out-of-bounds read vulnerability in Adobe Substance3D Painter versions 10.1.0 and earlier allows disclosure of sensitive memory contents when a victim opens a malicious file, potentially enabling attackers to leak memory addresses and bypass ASLR mitigations.
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.
-
Check if Adobe Substance 3D Painter is installedOn Windows: Check for the application in Start Menu or look for installation folder (typically C:\Program Files\Adobe\Adobe Substance 3D Painter). On macOS: Check /Applications folder for Adobe Substance 3D Painter.appAffected if The application is not installed on the system, then not affected by this CVE in its current form.
-
Identify the installed version numberWindows: Right-click the application shortcut, select Properties, and check the Details tab for version info. Or launch the application and go to Help > About Adobe Substance 3D Painter. macOS: Right-click the app in Applications, select Get Info, or launch and check Help > About.Affected if Version is 10.1.0 or earlier (any version below 10.1.1) - this means the installed version falls within the affected range.
-
Verify version against CVE-affected rangeCompare the identified version number to 10.1.1. The affected versions are any release below 10.1.1, including 10.1.0, 10.0.x, and all earlier major versions.Affected if Installed version is less than 10.1.1 (for example, 10.1.0, 10.0.0, 8.x, etc.) - the system is vulnerable to the out-of-bounds read when processing malicious files.
-
Confirm file open functionality is availableVerify the software can open project files (.sbsar, .sbs, or custom painter project formats). The vulnerability triggers specifically when opening a maliciously crafted file.Affected if The software can open files and the version is < 10.1.1 - the vulnerability is exploitable through malicious file handling.
User is affected if Adobe Substance 3D Painter is installed with any version below 10.1.1, as the out-of-bounds read flaw exists in all versions up to and including 10.1.0 and can be triggered by opening a specially crafted malicious file.
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
Update Substance3D Painter to a version newer than 10.1.0 when Adobe releases the patch; instruct users to avoid opening files from untrusted sources.
Substance 3D Painter 10.1.1 or later
- Close Substance 3D Painter if it is currently running
- Navigate to the official Adobe website and download Substance 3D Painter version 10.1.1 or later
- Run the Adobe installer and follow the on-screen prompts to complete the upgrade
- Restart Substance 3D Painter after the upgrade is complete
- Verify the installed version by checking Help > About in the application menu
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47435 — 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-47435 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