Cyber Resilience

CVE-2024-47438

Memory Safety in Adobe Substance 3D Painter ≤ 10.1.1

Memory Safety
Published
12 November 2024
Modified
13 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.0022 12th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2024-47438 is a medium-severity Write-what-where Condition (CWE-123) vulnerability in Adobe Substance 3D Painter. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-16 (Memory Protection) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Substance3D - Painter versions 10.1.0 and earlier are affected by a Write-what-where Condition vulnerability that could lead to a memory leak. This vulnerability allows an attacker to write a controlled value at a controlled memory location, which could result in…

more

the disclosure of sensitive memory content. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

CWE(s)
CWE-123CWE-787

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-20741Same product: Adobe Substance 3D Painter
CVE-2025-24450Same product: Adobe Substance 3D Painter
CVE-2024-49522Same product: Adobe Substance 3D Painter
CVE-2024-30307Same product: Adobe Substance 3D Painter
CVE-2024-47428Same product: Adobe Substance 3D Painter
CVE-2024-47430Same product: Adobe Substance 3D Painter
CVE-2024-47427Same product: Adobe Substance 3D Painter
CVE-2023-29285Same product: Adobe Substance 3D Painter
CVE-2024-49516Same product: Adobe Substance 3D Painter
CVE-2024-47433Same product: Adobe Substance 3D Painter

Affected Assets

adobe
substance 3d painter
≤ 10.1.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

SI-16 Memory Protection good match

Memory-protection mechanisms block unauthorized writes to arbitrary locations even if a write-what-where primitive exists.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require memory-safe coding and bounds checking that eliminate the root cause of write-what-where flaws.

SC-39 Process Isolation partial match

Process isolation confines the blast radius of an arbitrary write so it cannot affect other domains.

SI-10 Information Input Validation partial match

Input validation directly stops malformed data from triggering buffer overflows that produce arbitrary write-what-where conditions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent arbitrary write conditions via safe coding, bounds checking, and memory-safe constructs.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect write-what-where conditions before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices directly reduce the likelihood of write-what-where flaws such as buffer overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate input validation and bounds checking that mitigate arbitrary write conditions.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles discourage unsafe memory handling that leads to write-what-where vulnerabilities.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer operations that enable arbitrary memory writes.

A.8.32 Change management partial match
prevents

Change management processes help ensure security fixes for such weaknesses are properly deployed.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248592 OL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-123
RHEL 8 (1 rule)
  • V-230279 RHEL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-123
Windows 10 (1 rule)
  • V-220727 Structured Exception Handling Overwrite Protection (SEHOP) must be enabled. prevents CWE-123
Windows 11 (1 rule)
  • V-253284 Structured Exception Handling Overwrite Protection (SEHOP) must be enabled. prevents CWE-123

References