dbcve.org
Substance 3d PainterApplication · Adobe

CVE-2024-47433

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

Substance3D Painter versions 10.1.0 and earlier contain an out-of-bounds write vulnerability that allows an attacker to write data beyond allocated memory boundaries. Successful exploitation enables arbitrary code execution within the context of the current user. The attack vector requires the victim to open a maliciously crafted file, indicating a file-parsing vulnerability.

MitigationUsers should avoid opening files from untrusted or unknown sources. Organizations should ensure Substance3D Painter is updated to a patched version once released by Adobe. Apply vendor security updates as soon as they become available.

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. Determine if Adobe Substance 3D Painter is installed
    Check for the presence of Adobe Substance 3D Painter in your system applications or installed programs list. On Windows, this can be done via Control Panel > Programs and Features or Settings > Apps. On macOS, check /Applications folder or via Spotlight search.
    Affected if Adobe Substance 3D Painter is present on the system
  2. Identify the installed version of Adobe Substance 3D Painter
    Open Adobe Substance 3D Painter and navigate to Help > About or check the application properties in your system's installed programs list to view the exact version number.
    Affected if The version displayed is 10.1.0 or any earlier version
  3. Compare your version against the fixed release
    Review the version number identified in the previous step. The patched version is 10.1.1. Any version below 10.1.1 falls within the affected range.
    Affected if The installed version is earlier than 10.1.1 (for example, 10.1.0, 10.0.x, or earlier)
  4. Verify the attack vector exposure
    Assess whether the system opens files received from external or untrusted sources using Adobe Substance 3D Painter. The vulnerability is triggered specifically when opening a maliciously crafted file.
    Affected if Users on the system open files from untrusted or unknown sources using Substance 3D Painter

You are affected if Adobe Substance 3D Painter is installed and the version is 10.1.0 or earlier (prior to the 10.1.1 patch), especially if the application is used to open files from 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

Users should avoid opening files from untrusted or unknown sources. Organizations should ensure Substance3D Painter is updated to a patched version once released by Adobe. Apply vendor security updates as soon as they become available.

Recommended fix High confidence

Adobe Substance 3D Painter 10.1.1

  1. Check the current version of Adobe Substance 3D Painter by opening the application and navigating to Help > About, or checking in the Creative Cloud desktop app
  2. Close Adobe Substance 3D Painter if it is currently running
  3. Download Adobe Substance 3D Painter version 10.1.1 or later from the official Adobe website at helpx.adobe.com or through the Adobe 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 checking that the version now shows 10.1.1 or later

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

Fix this in Substance 3d Painter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47433 — 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-47433 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