Application crash via invalid TIFF memory write
Published Nov 10, 2021 · Updated Aug 4, 2024
Out-of-bounds write in WildBit Software WildBit Viewer 6.6 allows attackers to crash the application via a crafted TIFF image. The faulting instruction in Editor!TMethodImplementationIntercept+0x3c3682 writes a 16-bit value through the address in EBX without establishing that the destination is valid. Exploitation requires user interaction to open the malicious image, and the documented consequence is an application crash without reported confidentiality or integrity impact.
Summary
What happened
Out-of-bounds write in WildBit Software WildBit Viewer 6.6 allows attackers to crash the application via a crafted TIFF image. The faulting instruction in Editor!TMethodImplementationIntercept+0x3c3682 writes a 16-bit value through the address in EBX without establishing that the destination is valid. Exploitation requires user interaction to open the malicious image, and the documented consequence is an application crash without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2020-23893
- Published
- Nov 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- TIFF write-access-violation demonstrationproof 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