Sensitive-memory disclosure via malicious file processing
Published Jan 10, 2024 · Updated Jun 17, 2025
Out-of-bounds read in Adobe Substance 3D Stager 2.1.3 and earlier allows attackers to disclose sensitive memory via a malicious file. Adobe has not disclosed the affected parser, file format, or bounds-checking operation that reads beyond its intended buffer. Exploitation requires a victim to open the file; the reported consequence is memory disclosure that can weaken ASLR, not modification or service interruption.
Summary
What happened
Out-of-bounds read in Adobe Substance 3D Stager 2.1.3 and earlier allows attackers to disclose sensitive memory via a malicious file. Adobe has not disclosed the affected parser, file format, or bounds-checking operation that reads beyond its intended buffer. Exploitation requires a victim to open the file; the reported consequence is memory disclosure that can weaken ASLR, not modification or service interruption.
The record
- CVE
- CVE-2024-20715
- Published
- Jan 10, 2024
- Updated
- Jun 17, 2025
- Vendor
- Adobe
- Product
- Substance 3D Stager
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.1.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo