Application crash via crafted PSD processing
Published Nov 10, 2021 · Updated Aug 4, 2024
Out-of-bounds write in WildBit Viewer 6.6 allows attackers to crash the application by opening a crafted PSD image file. The PSD parsing path reaches Editor!TMethodImplementationIntercept+0x53f6c3 and executes a byte write through an invalid address. Exploitation requires a user to open the malicious image, and the documented consequence is termination of the viewer process without reported data disclosure or code execution.
Summary
What happened
Out-of-bounds write in WildBit Viewer 6.6 allows attackers to crash the application by opening a crafted PSD image file. The PSD parsing path reaches Editor!TMethodImplementationIntercept+0x53f6c3 and executes a byte write through an invalid address. Exploitation requires a user to open the malicious image, and the documented consequence is termination of the viewer process without reported data disclosure or code execution.
The record
- CVE
- CVE-2020-23888
- 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
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