dbcve.org
Substance 3d PainterApplication · Adobe

CVE-2024-53957

HIGH · 7.8 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to 10.1.2 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.1 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

A heap-based buffer overflow vulnerability exists in the file parsing component of Adobe Substance3D Painter versions 10.1.1 and earlier. When a user opens a specially crafted malicious file, the buffer overflow can be triggered, allowing an attacker to execute arbitrary code in the context of the current user.

MitigationDo not open untrusted or unsolicited files in Substance3D Painter. Update to a version newer than 10.1.1 once Adobe releases the security patch. Apply the vendor update as soon as 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.2

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 Substance3D Painter is installed
    Check for the presence of Adobe Substance3D Painter in your system applications or installed programs list. Look for the application in the Start menu, Applications folder, or control panel/program list.
    Affected if The application is installed on the system
  2. Determine the installed version number
    Open Adobe Substance3D Painter and navigate to Help > About, or check the application metadata in your system. The version number is typically displayed in the format 10.x.x
    Affected if The version cannot be determined or is older than 10.1.2
  3. Compare against vulnerable version range
    Compare your installed version against the affected range: versions 10.1.1 and earlier are vulnerable. Version 10.1.2 and later contain the security fix.
    Affected if The installed version is 10.1.1 or earlier (any version below 10.1.2)
  4. Assess file handling exposure
    Consider whether the application is used to open files from untrusted or unsolicited sources. The vulnerability is triggered when the file parsing component processes a specially crafted malicious file.
    Affected if Users open files from untrusted or unknown sources in Substance3D Painter

You are affected if Adobe Substance3D Painter version 10.1.1 or earlier is installed and users open files in the application.

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.2 or later
Fixed in 10.1.2
Interim mitigation

Do not open untrusted or unsolicited files in Substance3D Painter. Update to a version newer than 10.1.1 once Adobe releases the security patch. Apply the vendor update as soon as available.

Recommended fix High confidence

Substance 3D Painter 10.1.2

  1. Open Adobe Creative Cloud desktop application or navigate to Adobe's official Substance 3D Painter download page
  2. Check the current installed version of Substance 3D Painter (Help > About in the application menu)
  3. Download Substance 3D Painter version 10.1.2 or later from Adobe's official website or through the Creative Cloud desktop application
  4. Close any running instances of Substance 3D Painter
  5. Run the installer and follow the on-screen prompts to complete the upgrade
  6. Verify the upgrade was successful by checking the version number in the application (Help > About)

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
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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