dbcve.org
Substance 3d PainterApplication · Adobe

CVE-2024-49525

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 contains a heap-based buffer overflow vulnerability that can be triggered when a user opens a maliciously crafted file, leading to arbitrary code execution in the context of the current user.

MitigationRestrict opening of untrusted or unsolicited files in Substance3D Painter until Adobe releases an official patch; consider application whitelisting or sandboxing as compensating controls.

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 Substance3D Painter is installed
    On Windows, check in Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Adobe Substance 3D Painter' or look for the application in Program Files/Adobe. On macOS, check /Applications for Adobe Substance 3D Painter.app
    Affected if The application is present on the system
  2. Determine the installed version number
    Open the application's main executable (Substance 3D Painter.exe or Substance 3D Painter.app), then access Help > About or the application's info panel to display the version. On Windows, you can also right-click the executable, select Properties, and view the Details tab for Product Version
    Affected if A version number is displayed
  3. Compare version against affected range
    Check if the installed version is less than 10.1.1. Vulnerable versions are 10.1.0 and earlier. The fixed version is 10.1.1
    Affected if The installed version is 10.1.0 or any earlier version (e.g., 10.0.x, 9.x)
  4. Confirm file import feature is accessible
    Verify the application can open project files (.spproj, .sbsar) or other importable file types. The vulnerability triggers when opening a maliciously crafted file, so the file import functionality must be available
    Affected if File import or open functionality is enabled and usable

If Adobe Substance3D Painter is installed with a version before 10.1.1 and the application can open files, the environment is affected by this heap-based buffer overflow vulnerability.

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

Restrict opening of untrusted or unsolicited files in Substance3D Painter until Adobe releases an official patch; consider application whitelisting or sandboxing as compensating controls.

Recommended fix Moderate confidence

Adobe Substance 3D Painter 10.1.1 or later

  1. 1. Close Adobe Substance 3D Painter if it is currently running
  2. 2. Backup any custom brushes, textures, and project files as a precaution
  3. 3. Navigate to the Adobe Creative Cloud desktop application or visit helpx.adobe.com
  4. 4. Locate Adobe Substance 3D Painter in the available applications
  5. 5. Check for available updates or download version 10.1.1 from Adobe's official website
  6. 6. Run the installer and follow the on-screen prompts to complete the upgrade
  7. 7. After installation, verify the version by opening Substance 3D Painter and checking 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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