CVE-2024-45142
Adobe Substance 3D Stager ≤ 3.0.4
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-45142 is a high-severity Write-what-where Condition (CWE-123) vulnerability in Adobe Substance 3D Stager. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 23th 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 SI-16 (Memory Protection) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-41326
Vulnerability Data
Substance3D - Stager versions 3.0.3 and earlier are affected by a Write-what-where Condition vulnerability that could allow an attacker to execute arbitrary code in the context of the current user. This vulnerability allows an attacker to write a controlled value…
more
to an arbitrary memory location, potentially leading to code execution. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 4 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Memory-protection mechanisms block unauthorized writes to arbitrary locations even if a write-what-where primitive exists.
Secure engineering principles require memory-safe coding and bounds checking that eliminate the root cause of write-what-where flaws.
Process isolation confines the blast radius of an arbitrary write so it cannot affect other domains.
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.
Secure SDLC practices directly prevent arbitrary write conditions via safe coding, bounds checking, and memory-safe constructs.
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.
Security testing in development and acceptance can detect write-what-where conditions before deployment.
Secure development lifecycle practices directly reduce the likelihood of write-what-where flaws such as buffer overflows.
Application security requirements can mandate input validation and bounds checking that mitigate arbitrary write conditions.
Secure architecture and engineering principles discourage unsafe memory handling that leads to write-what-where vulnerabilities.
Secure coding standards explicitly forbid unsafe buffer operations that enable arbitrary memory writes.
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