Code execution via malicious file out-of-bounds write
Published Mar 11, 2025 · Updated Mar 11, 2025
Out-of-bounds write in Adobe Substance 3D Sampler 4.5.2 and earlier allows attackers to execute code when a user opens a malicious file. Adobe identifies the memory error as an out-of-bounds write but has not disclosed the affected parser, file format, or unchecked operation that writes past its buffer. A user must open the crafted file; successful exploitation runs code with the current user's privileges and can fully compromise that user's data and session.
Summary
What happened
Out-of-bounds write in Adobe Substance 3D Sampler 4.5.2 and earlier allows attackers to execute code when a user opens a malicious file. Adobe identifies the memory error as an out-of-bounds write but has not disclosed the affected parser, file format, or unchecked operation that writes past its buffer. A user must open the crafted file; successful exploitation runs code with the current user's privileges and can fully compromise that user's data and session.
The record
- CVE
- CVE-2025-24441
- Published
- Mar 11, 2025
- Updated
- Mar 11, 2025
- Vendor
- Adobe
- Product
- Substance 3D Sampler
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2025CVE publishedPublication date reported by the CVE source.
- Mar 11, 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 <=4.5.2
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.
Weakness, pattern, technique
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