Code execution via undisclosed out-of-bounds write
Published Jan 14, 2025 · Updated Feb 12, 2025
Out-of-bounds write in Adobe Substance 3D Stager 3.0.4 and earlier allows local users to execute code via a malicious file. Adobe has not published the affected parser, file format, or the bounds-checking operation that writes beyond its intended buffer. A victim must open the file, and resulting code runs in the current user's context.
Summary
What happened
Out-of-bounds write in Adobe Substance 3D Stager 3.0.4 and earlier allows local users to execute code via a malicious file. Adobe has not published the affected parser, file format, or the bounds-checking operation that writes beyond its intended buffer. A victim must open the file, and resulting code runs in the current user's context.
The record
- CVE
- CVE-2025-21130
- Published
- Jan 14, 2025
- Updated
- Feb 12, 2025
- Vendor
- Adobe
- Product
- Substance 3D Stager
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 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 <=3.0.4
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