CVE-2024-47433 Overview
CVE-2024-47433 is an out-of-bounds write vulnerability [CWE-787] affecting Adobe Substance 3D Painter versions 10.1.0 and earlier. Successful exploitation allows arbitrary code execution in the context of the current user. The attack requires local access and user interaction, specifically opening a malicious project or asset file crafted by an attacker.
Adobe published the fix in security bulletin APSB24-86 on November 12, 2024. The vulnerability carries a CVSS 3.1 base score of 7.8. Neither CISA KEV listing nor public proof-of-concept code exists for this issue at the time of publication.
Critical Impact
Arbitrary code execution as the logged-in user through a malicious file, enabling malware deployment, credential theft, or lateral movement from a 3D artist's workstation.
Affected Products
- Adobe Substance 3D Painter 10.1.0
- Adobe Substance 3D Painter versions prior to 10.1.0
- Windows and macOS installations of the affected builds
Discovery Timeline
- 2024-11-12 - Adobe releases security bulletin APSB24-86
- 2024-11-12 - CVE-2024-47433 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-47433
Vulnerability Analysis
CVE-2024-47433 is classified as an out-of-bounds write [CWE-787]. This class of memory corruption occurs when an application writes data past the end, or before the beginning, of an allocated buffer. In Substance 3D Painter, the flaw is triggered during parsing of a maliciously crafted file the user opens.
Writing outside allocated memory can overwrite adjacent heap metadata, function pointers, or object virtual tables. An attacker who controls the corrupted data can pivot memory corruption into arbitrary code execution in the running process. Because Substance 3D Painter runs with the user's privileges, executed code inherits those rights.
Adobe's advisory confirms the impact is arbitrary code execution in the context of the current user. Confidentiality, integrity, and availability are all rated High under the CVSS vector.
Root Cause
The root cause is missing or incorrect bounds validation when the application parses attacker-controlled fields inside a project or asset file. Substance 3D Painter processes complex 3D scene, texture, and material data formats. Any length, index, or offset field consumed without validation against the destination buffer size can produce an out-of-bounds write.
Adobe has not published field-level technical details in the advisory. See the Adobe Security Advisory APSB24-86 for vendor guidance.
Attack Vector
The attack vector is Local with required user interaction. An attacker must deliver a crafted Substance 3D Painter file, typically through phishing email, a compromised asset marketplace, a shared project drive, or a supply-chain modification of legitimate assets. The victim must open the file in a vulnerable version to trigger the flaw. No network exposure or elevated privileges are required.
Detection Methods for CVE-2024-47433
Indicators of Compromise
- Substance 3D Painter (Adobe Substance 3D Painter.exe) spawning unexpected child processes such as cmd.exe, powershell.exe, wscript.exe, or shells on macOS.
- Unexpected outbound network connections originating from the Substance 3D Painter process shortly after a file open event.
- Crash dumps or Windows Error Reporting events referencing Substance 3D Painter following the opening of externally sourced project files.
- Substance 3D Painter files (.spp, .spt, .sbsar) arriving from untrusted email senders, forums, or asset marketplaces.
Detection Strategies
- Hunt for process lineage where Substance 3D Painter is the parent of interpreter or scripting binaries. Legitimate workflows rarely produce this chain.
- Correlate file-open telemetry on Substance 3D Painter file extensions with subsequent process creation and network events on the same host.
- Inventory installed Substance 3D Painter versions across creative workstations and flag any build at or below 10.1.0.
Monitoring Recommendations
- Enable command-line and process-creation logging on workstations used by 3D artists and visual effects teams.
- Forward endpoint telemetry to a centralized data lake so file-open, process, and network events can be joined during investigations.
- Alert on Substance 3D Painter crashes originating from files located in downloads, email attachment cache, or removable media paths.
How to Mitigate CVE-2024-47433
Immediate Actions Required
- Upgrade Adobe Substance 3D Painter to version 10.1.1 or later on all Windows and macOS endpoints, per Adobe bulletin APSB24-86.
- Identify vulnerable installations through software inventory and prioritize workstations that routinely open third-party or downloaded project files.
- Instruct users to open Substance 3D Painter files only from trusted internal sources until patching is complete.
Patch Information
Adobe fixed CVE-2024-47433 in Substance 3D Painter version 10.1.1. Full remediation details are available in the Adobe Security Advisory APSB24-86. Apply the update through the Adobe Creative Cloud desktop application or Adobe Admin Console for managed deployments.
Workarounds
- Block execution of unpatched Substance 3D Painter builds through application allowlisting until updates are installed.
- Restrict the download and opening of Substance 3D files from external sources through email gateway and web proxy policies.
- Run Substance 3D Painter under standard user accounts, never with administrative rights, to limit the impact of successful exploitation.
# Verify installed Substance 3D Painter version on Windows via PowerShell
Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object { $_.DisplayName -like "*Substance 3D Painter*" } |
Select-Object DisplayName, DisplayVersion, InstallLocation
# Verify installed version on macOS
mdls -name kMDItemVersion "/Applications/Adobe Substance 3D Painter/Adobe Substance 3D Painter.app"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

