Heysoft EventSave 5.1 and 5.2 and Heysoft EventSave+ 5.1 and 5.2 does not check whether the log file can be written to, which allows attackers to prevent events from being recorded by opening the log file using an application such as Microsofts Event Viewer.
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Eventsave | Heysoft | 5.1 (including) | 5.1 (including) |
| Eventsave | Heysoft | 5.2 (including) | 5.2 (including) |
| Eventsave+ | Heysoft | 5.1 (including) | 5.1 (including) |
| Eventsave+ | Heysoft | 5.2 (including) | 5.2 (including) |
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.