dbcve.org
Substance 3d PainterApplication · Adobe

CVE-2024-47429

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 10.1.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Substance3D - Painter versions 10.1.0 and earlier are affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. 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 confidence

An out-of-bounds write vulnerability in Adobe Substance3D Painter versions 10.1.0 and earlier allows arbitrary code execution when a user opens a malicious file. The vulnerability stems from improper bounds checking during file parsing, enabling an attacker to write data beyond allocated memory boundaries.

MitigationUpdate Substance3D Painter to a version newer than 10.1.0. Avoid opening untrusted or unexpected files from unknown sources until the patch is applied.

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
Substance 3d PainterApplication
Affected:< 10.1.1

CVSS 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Adobe Substance 3D Painter is installed
    Check for the application in typical installation directories: Windows typically at 'C:\Program Files\Adobe\Adobe Substance 3D Painter' or check the Windows Start Menu/Applications list. On macOS, check '/Applications/Adobe Substance 3D Painter' or the Applications folder.
    Affected if The application is present on the system
  2. Determine the installed version number
    Locate the application executable and check its version properties. On Windows, right-click the executable, select Properties, then view the Details tab for Version info. On macOS, right-click the app in Finder, select Get Info, and check the Version field. Alternatively, launch the application and look for version info in the Help > About menu.
    Affected if The displayed version is 10.1.0 or earlier, or the version field shows no version (unrecognized version)
  3. Compare installed version against the affected range
    The affected versions are anything below 10.1.1. If your version is 10.1.0, 10.0.x, or any earlier version, you are running a vulnerable release.
    Affected if Installed version is 10.1.0 or earlier (versions prior to 10.1.1)
  4. Assess file opening exposure
    The vulnerability is triggered when parsing malicious files. Determine if the system regularly opens .sbsar, .sbs, or other Substance files from untrusted or unknown sources, as this is the attack vector.
    Affected if Users routinely open Substance files from untrusted or unknown sources without prior validation

You are affected if Adobe Substance 3D Painter version 10.1.0 or earlier is installed on your system and users open Substance files from potentially untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.1.1 or later
Fixed in 10.1.1
Interim mitigation

Update Substance3D Painter to a version newer than 10.1.0. Avoid opening untrusted or unexpected files from unknown sources until the patch is applied.

Recommended fix High confidence

Substance 3D Painter 10.1.1

  1. Close any running instances of Substance 3D Painter
  2. Back up project files and settings as a precautionary measure
  3. Download Substance 3D Painter version 10.1.1 from the official Adobe website or through the Creative Cloud desktop application
  4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. Verify the upgrade was successful by opening Substance 3D Painter and checking Help > About to confirm version 10.1.1 is installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Substance 3d Painter Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47429 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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