dbcve.org
Substance 3d PainterApplication · Adobe

CVE-2024-20787

MEDIUM · 5.5 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 10.1.0 or later.
See remediation →
58/100
Remediation priority · Elevated
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.0.1 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 · moderate confidence

An out-of-bounds read vulnerability in Substance3D Painter versions 10.0.1 and earlier allows reading memory beyond allocated buffer boundaries when parsing specially crafted files. This can expose sensitive memory contents and potentially aid in bypassing ASLR as an initial information disclosure step. Exploitation requires user interaction to open a malicious file.

MitigationApply the vendor patch when released. Until then, instruct users not to open files from untrusted sources. Consider implementing additional file validation heuristics at the enterprise perimeter.

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.0

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 installation
    Check for the application in typical installation paths: Windows: C:\Program Files\Adobe\Adobe Substance 3D Painter or C:\Program Files (x86)\Adobe\Adobe Substance 3D Painter. On macOS: /Applications/Adobe Substance 3D Painter. Use file explorer or command: dir 'C:\Program Files\Adobe' or ls /Applications | grep -i substance
    Affected if The application is installed on the system
  2. Identify installed version number
    On Windows: Right-click the executable Adobe Substance 3D Painter.exe, select Properties, then go to Details tab to view File Version or Product Version. Alternatively, run: wmic product where 'name like "%Substance%"' get version. On macOS: Right-click Adobe Substance 3D Painter.app, Show Package Contents, open Info.plist and check CFBundleShortVersionString
    Affected if The version displayed is 10.0.1 or earlier, or any version below 10.1.0
  3. Confirm patch status via application update mechanism
    Launch Adobe Substance 3D Painter, then go to Help > Check for Updates or Help > Updates to see if version 10.1.0 or later is available. If update check fails or shows no update available, the installed version may still be vulnerable
    Affected if No update to version 10.1.0 or later is available and the installed version is below 10.1.0
  4. Review file association and handling
    Check which file types are associated with Substance 3D Painter by examining Windows Registry key HKEY_CLASSES_ROOT\.sbsar or HKEY_CURRENT_USER\Software\Adobe\Substance 3D Painter, or on macOS via Get Info on a .sbsar file. Note that exploitation requires a user to open a specially crafted malicious file
    Affected if The application is configured to open .sbsar or related Substance files from untrusted sources

A system is affected if Adobe Substance 3D Painter is installed and the installed version is 10.0.1 or any version prior to 10.1.0, and the application is used to open files.

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.0 or later
Fixed in 10.1.0
Interim mitigation

Apply the vendor patch when released. Until then, instruct users not to open files from untrusted sources. Consider implementing additional file validation heuristics at the enterprise perimeter.

Recommended fix High confidence

10.1.0

  1. Open Adobe Creative Cloud desktop application or navigate to the Adobe Substance 3D Painter product page
  2. Check the current installed version of Substance 3D Painter (Help > About in the application)
  3. If version is below 10.1.0, locate the update option in Adobe Creative Cloud
  4. Update Substance 3D Painter to version 10.1.0 or later
  5. Restart the application after the update completes
  6. Verify the installed version is 10.1.0 or higher

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

Fix this in Substance 3d Painter Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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