CVE-2024-47437
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 confidenceOut-of-bounds read vulnerability in Adobe Substance3D Painter versions 10.1.0 and earlier allows disclosure of sensitive memory contents when processing a malicious file. This memory disclosure can be leveraged to bypass ASLR (Address Space Layout Randomization) mitigations, potentially facilitating further exploitation. The attack requires user interaction as the victim must open a specially crafted malicious 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< 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.
-
Locate the Adobe Substance3D Painter installationFind the installed application in your system's program list (Windows: Control Panel > Programs and Features, macOS: Applications folder, or search for 'Substance 3D Painter' in your system).Affected if The application is installed on the system.
-
Determine the installed version numberOpen Adobe Substance3D Painter and navigate to Help > About (or check the application properties/executable file details). Alternatively, check the Windows Programs and Features list or macOS Applications folder for the version displayed alongside the application name.Affected if You can retrieve a version number from the application.
-
Compare your version against the affected rangeCompare the installed version to the vulnerable range: versions 10.1.0 and earlier are affected. The fix is in version 10.1.1 and later.Affected if The installed version is 10.1.0 or earlier (anything below 10.1.1).
-
Assess exposure to malicious filesConsider whether users in your environment typically open .sbsar, .sbs, or other Substance files from untrusted or unknown sources, as the vulnerability is triggered when processing a specially crafted malicious file.Affected if Users routinely open Substance files from untrusted sources without verification.
You are affected if Adobe Substance3D Painter version 10.1.0 or earlier is installed on your system.
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 (or latest available). Additionally, exercise caution when opening files from untrusted sources and consider disabling file previews in the application.
Adobe Substance 3D Painter 10.1.1
- 1. Open Adobe Substance 3D Painter application
- 2. Navigate to the Help menu or Check for Updates option
- 3. Alternatively, download Substance 3D Painter version 10.1.1 or later from the official Adobe website
- 4. Install the updated version, ensuring you close the application if prompted
- 5. Verify the installed version matches 10.1.1 or higher to confirm the vulnerability is addressed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47437 — 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-47437 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