CVE-2023-29273
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 · uneditedAdobe Substance 3D Painter versions 8.3.0 (and earlier) is affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 confidenceAdobe Substance 3D Painter versions 8.3.0 and earlier contain an out-of-bounds read vulnerability during file parsing. When the application parses a specially crafted malicious file, it reads beyond the bounds of allocated memory structures, potentially allowing an attacker to leak sensitive memory contents and ultimately achieve code execution in the context of the current user.
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<= 8.3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Adobe Substance 3D Painter versionOpen the application, then go to Help > About Adobe Substance 3D Painter, or check the version listed in the application installer or installed programs list in Control Panel/System SettingsAffected if If the version displayed is 8.3.0 or earlier (any version <= 8.3.0)
-
Confirm the application is vulnerable to file parsing attacksThis vulnerability is triggered when the application parses specially crafted .sbsar, .sbs, or other supported file formatsAffected if If the installed version is 8.3.0 or earlier, the application is vulnerable when parsing malicious files
-
Identify exposure to untrusted file sourcesReview whether the user or other users on the system open 3D asset files from untrusted or unknown sources, download files from the internet, or receive files via email or messagingAffected if If untrusted files are opened with Adobe Substance 3D Painter, exploitation becomes possible
The environment is affected if Adobe Substance 3D Painter version 8.3.0 or earlier is installed and the application is used to open files from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUsers should update Adobe Substance 3D Painter to version 8.3.1 or later. Until patched, users must avoid opening files from untrusted sources, as exploitation requires user interaction (opening a malicious file).
Latest version of Substance 3D Painter (version > 8.3.0, check Adobe for 8.3.1 or subsequent release)
- 1. Close Adobe Substance 3D Painter if it is currently running
- 2. Back up any custom assets, presets, or projects in the application data folder before upgrading
- 3. Download the latest version of Adobe Substance 3D Painter from the official Adobe website (substance3d.adobe.com) or through the Creative Cloud desktop application
- 4. Run the installer and follow the on-screen prompts to complete the installation
- 5. After installation, verify the installed version by opening Substance 3D Painter and navigating to Help > About to confirm the version is newer than 8.3.0
- 6. Test critical workflows with the new version before deploying to production environments
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29273 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29273 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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