Code execution via malicious-file out-of-bounds write
Published Oct 9, 2024 · Updated Oct 9, 2024
Out-of-bounds write in Adobe Substance 3D Stager 3.0.3 and earlier allows attackers to execute code through a malicious file. Adobe identifies the corruption class but does not disclose the affected parser, file format, or bounds-checking error that permits the write. A victim must open the file, after which code runs in the context of the current user.
Summary
What happened
Out-of-bounds write in Adobe Substance 3D Stager 3.0.3 and earlier allows attackers to execute code through a malicious file. Adobe identifies the corruption class but does not disclose the affected parser, file format, or bounds-checking error that permits the write. A victim must open the file, after which code runs in the context of the current user.
The record
- CVE
- CVE-2024-45140
- Published
- Oct 9, 2024
- Updated
- Oct 9, 2024
- Vendor
- Adobe
- Product
- Substance 3D Stager
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 9, 2024Record 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.3
- 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.
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