Application crash via malformed CUR file parsing
Published Mar 18, 2021 · Updated Aug 3, 2024
Memory corruption in FastStone Image Viewer 7.5 and earlier allows local users to crash FSViewer.exe by opening a malformed CUR file. The CUR parser mishandles crafted file data and performs a user-mode write near NULL at address 0x005bdfc9. Exploitation requires a user to open or view the file; the documented result is an FSViewer.exe crash, while code execution remains unverified.
Summary
What happened
Memory corruption in FastStone Image Viewer 7.5 and earlier allows local users to crash FSViewer.exe by opening a malformed CUR file. The CUR parser mishandles crafted file data and performs a user-mode write near NULL at address 0x005bdfc9. Exploitation requires a user to open or view the file; the documented result is an FSViewer.exe crash, while code execution remains unverified.
The record
- CVE
- CVE-2021-26235
- Published
- Mar 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2021CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- VoidSec malformed CUR proof of conceptproof of concept · demonstrated
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