Substance 3d PainterApplication · Adobe

CVE-2024-47431

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 a Heap-based Buffer Overflow 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

Adobe Substance3D Painter versions 10.1.0 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a specially crafted malicious file, leading to arbitrary code execution in the context of the current user.

MitigationUpgrade Adobe Substance3D Painter to a version newer than 10.1.0. Users should avoid opening untrusted files 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. Identify installed Adobe Substance3D Painter version
    Open the application and navigate to Help > About, or check the installed version via the system installer or application metadata
    Affected if The version shown is 10.1.0 or earlier (any version prior to 10.1.1)
  2. Compare version against CVE affected range
    Verify the installed version number against the affected range: versions < 10.1.1 are vulnerable
    Affected if The installed version is less than 10.1.1
  3. Assess file opening behavior
    Review recent file open activity in the application - check logs, recent documents, or application usage history if available
    Affected if The application was used to open files from untrusted or unknown sources since the vulnerability was disclosed
  4. Verify patch status
    Check if Adobe Substance3D Painter has received any updates by opening the application and checking for updates via Help > Check for Updates, or via the Creative Cloud desktop application
    Affected if No update to version 10.1.1 or later is available or installed

You are affected if Adobe Substance3D Painter version 10.1.0 or earlier is installed and the application has been used to open files, particularly 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

Upgrade Adobe Substance3D Painter to a version newer than 10.1.0. Users should avoid opening untrusted files until the patch is applied.

Recommended fix High confidence

10.1.1

  1. 1. Open Adobe Substance 3D Painter
  2. 2. Navigate to Help > About Adobe Substance 3D Painter to verify the current version
  3. 3. If the version is 10.1.0 or earlier, download the latest version from the official Adobe website or use the Adobe Creative Cloud desktop application to update
  4. 4. Install version 10.1.1 or later
  5. 5. After installation, verify the version by checking Help > About Adobe Substance 3D Painter

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47431 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