Insufficient policy enforcement in downloads in Google Chrome on Windows prior to 79.0.3945.79 allowed a local attacker to spoof downloaded files via local code.
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 |
|---|---|---|---|
| Chrome | * | 79.0.3945.79 (excluding) | |
| Red Hat Enterprise Linux 6 Supplementary | RedHat | chromium-browser-0:79.0.3945.79-1.el6_10 | * |
| Chromium-browser | Ubuntu | bionic | * |
| Chromium-browser | Ubuntu | devel | * |
| Chromium-browser | Ubuntu | disco | * |
| Chromium-browser | Ubuntu | eoan | * |
| Chromium-browser | Ubuntu | trusty | * |
| Chromium-browser | Ubuntu | upstream | * |
| Chromium-browser | Ubuntu | xenial | * |
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.