Vulnerabilities > Improper Locking
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2020-09-17 | CVE-2020-0357 | Improper Locking vulnerability in Google Android 11.0 In SurfaceFlinger, there is a possible use-after-free due to improper locking. | 4.6 |
| 2020-08-24 | CVE-2020-24606 | Improper Locking vulnerability in multiple products Squid before 4.13 and 5.x before 5.0.4 allows a trusted peer to perform Denial of Service by consuming all available CPU cycles during handling of a crafted Cache Digest response message. | 7.5 |
| 2020-05-20 | CVE-2020-13246 | Improper Locking vulnerability in Gitea An issue was discovered in Gitea through 1.11.5. | 5.0 |
| 2020-05-09 | CVE-2020-12771 | Improper Locking vulnerability in multiple products An issue was discovered in the Linux kernel through 5.6.11. | 4.9 |
| 2020-05-08 | CVE-2019-14898 | Improper Locking vulnerability in multiple products The fix for CVE-2019-11599, affecting the Linux kernel before 5.0.10 was not complete. | 7.0 |
| 2020-03-14 | CVE-2020-10573 | Improper Locking vulnerability in Meetecho Janus An issue was discovered in Janus through 0.9.1. | 5.0 |
| 2019-12-10 | CVE-2019-13762 | Improper Locking vulnerability in multiple products 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. | 3.3 |
| 2019-10-08 | CVE-2019-17343 | Improper Locking vulnerability in multiple products An issue was discovered in Xen through 4.11.x allowing x86 PV guest OS users to cause a denial of service or gain privileges by leveraging incorrect use of the HVM physmap concept for PV domains. | 4.6 |
| 2019-08-23 | CVE-2019-15513 | Improper Locking vulnerability in multiple products An issue was discovered in OpenWrt libuci (aka Library for the Unified Configuration Interface) before 15.05.1 as used on Motorola CX2L MWR04L 1.01 and C1 MWR03 1.01 devices. | 7.5 |
| 2019-08-07 | CVE-2019-14763 | Improper Locking vulnerability in multiple products In the Linux kernel before 4.16.4, a double-locking error in drivers/usb/dwc3/gadget.c may potentially cause a deadlock with f_hid. | 4.9 |