Substance 3d PainterApplication · Adobe

CVE-2023-29283

HIGH · 7.8 CVSS v3.1 Published 2023-05-11
Fix available
A fix is available. Upgrade to after 8.3.0 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
Adobe Substance 3D Painter versions 8.3.0 (and earlier) is 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 Substance 3D Painter versions 8.3.0 and earlier contains a heap-based buffer overflow vulnerability during file parsing. An attacker can craft a malicious file that, when opened by a victim, triggers the overflow and allows arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Substance 3D Painter to the latest patched version. Avoid opening .spp or project files from untrusted or unknown sources until the update 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:<= 8.3.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
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. Check if Adobe Substance 3D Painter is installed
    Look for the application in the system. On Windows, check Program Files or Program Files (x86) for 'Adobe Substance 3D Painter' folder. On macOS, check /Applications folder for 'Adobe Substance 3D Painter'.
    Affected if The application is present on the system
  2. Determine the installed version of Adobe Substance 3D Painter
    On Windows, open the application and go to Help > About, or check the version in the installer/registry. On macOS, right-click the app in Applications, select Get Info, and check the Version field. The version number is typically displayed in the format like 8.x.x.
    Affected if The version cannot be determined or is <= 8.3.0
  3. Verify the file parsing feature is accessible
    Confirm the application can open .spp files or project files. The vulnerability triggers during file parsing when a victim opens a maliciously crafted file.
    Affected if The application can open .spp or project files and the version is <= 8.3.0

A user is affected if Adobe Substance 3D Painter version 8.3.0 or earlier is installed and the application can open .spp or project files, allowing a maliciously crafted file to trigger the heap-based buffer overflow.

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 a release after 8.3.0
Interim mitigation

Update Adobe Substance 3D Painter to the latest patched version. Avoid opening .spp or project files from untrusted or unknown sources until the update is applied.

Recommended fix Moderate confidence

Adobe Substance 3D Painter 8.4.0 or later

  1. 1. Close Adobe Substance 3D Painter if it is currently running
  2. 2. Visit the official Adobe support website or the Adobe Creative Cloud desktop application
  3. 3. Check for available updates to Adobe Substance 3D Painter
  4. 4. Download and install the latest version of Adobe Substance 3D Painter (version 8.4.0 or later)
  5. 5. After installation, verify the version by opening the application and checking 'Help' > 'About' to confirm the version number
Caveat Users should review release notes for any changes to features or workflows; ensure project files are compatible with the new version

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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