Code execution via simulator use-after-free
Published Jun 14, 2022 · Updated Aug 3, 2024
Use-after-free in the V-SFT simulator before 6.1.6.0 allows attackers to disclose information or execute code through a crafted image file. Published advisories identify the simulator as the locus but do not disclose the freed object, function, or image-parsing operation. Exploitation requires a user to open the file, after which code runs in the user's application context or simulator memory is exposed.
Summary
What happened
Use-after-free in the V-SFT simulator before 6.1.6.0 allows attackers to disclose information or execute code through a crafted image file. Published advisories identify the simulator as the locus but do not disclose the freed object, function, or image-parsing operation. Exploitation requires a user to open the file, after which code runs in the user's application context or simulator memory is exposed.
The record
- CVE
- CVE-2022-29522
- Published
- Jun 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Fuji Electric
- Product
- V-SFT
- Classifications
- CWE-416, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=versions prior to v6.1.6.0
What conditions does exploitation require?
What is affected?
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