CVE-2024-47436
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 · moderate confidenceAn out-of-bounds read vulnerability exists in Substance3D Painter's file parsing logic. When a victim opens a specially crafted malicious file, the application reads memory beyond allocated buffer boundaries, leaking sensitive memory contents that can be used to defeat ASLR mitigation.
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.
-
Verify Adobe Substance 3D Painter installationCheck system for the presence of Adobe Substance 3D Painter. On Windows, look in common program directories or search for 'Substance 3D Painter' in Add/Remove Programs. On macOS, check /Applications folder.Affected if The software is installed on the system
-
Determine installed version numberOpen Substance 3D Painter and navigate to Help > About, or right-click the executable file and select Properties to view version details. The version is typically displayed as a three-part number like 10.0.x or 10.1.0.Affected if Installed version is lower than 10.1.1
-
Confirm file parsing is accessibleThe vulnerability lies in the application's file parsing logic. Verify the application can open and import project files (.spp, .fbx, .obj, etc.) by checking if the File > Open or File > Import menu options are available and functional.Affected if The application can open and parse external files (this is the application's core function)
-
Assess file handling exposureDetermine if the system handles files from untrusted or external sources. Check if the application is used to open files received via email, downloaded from the internet, or obtained from third parties.Affected if The user opens files from untrusted or unknown sources using the vulnerable software version
A system is affected if Adobe Substance 3D Painter is installed with a version lower than 10.1.1 and a user opens a specially crafted malicious file, which triggers the out-of-bounds read during file parsing.
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. Until a patch is available, exercise caution when opening files from untrusted sources.
10.1.1 or later
- Verify current Adobe Substance 3D Painter version by opening the application and checking 'Help' > 'About Adobe Substance 3D Painter'
- 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 version 10.1.1 or later using the Adobe Creative Cloud desktop application or the standalone installer
- After installation, verify the new version by checking 'Help' > 'About Adobe Substance 3D Painter' to confirm version 10.1.1 or later is installed
- Exercise caution when opening files from untrusted sources, as exploitation requires user interaction with a malicious file
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47436 — 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-47436 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