Code execution via malicious file heap overflow
Published Mar 11, 2025 · Updated Mar 12, 2025
Heap-based buffer overflow in Adobe Substance 3D Sampler 4.5.2 and earlier allows attackers to execute code via a malicious file. Adobe identifies the flaw as a heap-based buffer overflow but has not published the affected parser, file format, or faulty memory operation. A victim must open the file; successful exploitation runs code in the current user's context, allowing access and changes within that account's permissions.
Summary
What happened
Heap-based buffer overflow in Adobe Substance 3D Sampler 4.5.2 and earlier allows attackers to execute code via a malicious file. Adobe identifies the flaw as a heap-based buffer overflow but has not published the affected parser, file format, or faulty memory operation. A victim must open the file; successful exploitation runs code in the current user's context, allowing access and changes within that account's permissions.
The record
- CVE
- CVE-2025-24439
- Published
- Mar 11, 2025
- Updated
- Mar 12, 2025
- Vendor
- Adobe
- Product
- Substance 3D Sampler
- Classifications
- CWE-122, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2025CVE publishedPublication date reported by the CVE source.
- Mar 12, 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