Vulnerabilities > Improper Locking

DATE CVE VULNERABILITY TITLE RISK
2021-06-21 CVE-2021-0529 Improper Locking vulnerability in Google Android
In memory management driver, there is a possible memory corruption due to improper locking.
local
low complexity
google CWE-667
4.6
2021-04-29 CVE-2021-31427 Improper Locking vulnerability in Parallels Desktop 15.1.547309
This vulnerability allows local attackers to disclose sensitive information on affected installations of Parallels Desktop 15.1.5-47309.
1.9
2021-04-29 CVE-2021-31422 Improper Locking vulnerability in Parallels Desktop 16.1.149141
This vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop 16.1.1-49141.
4.4
2021-04-01 CVE-2021-20291 Improper Locking vulnerability in multiple products
A deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1.
7.1
2020-12-31 CVE-2020-12658 Improper Locking vulnerability in multiple products
** DISPUTED ** gssproxy (aka gss-proxy) before 0.8.3 does not unlock cond_mutex before pthread exit in gp_worker_main() in gp_workers.c.
network
low complexity
gssproxy-project debian CWE-667
7.5
2020-12-15 CVE-2020-27035 Improper Locking vulnerability in Google Android 11.0
In priorLinearAllocation of C2AllocatorIon.cpp, there is a possible use-after-free due to improper locking.
local
low complexity
google CWE-667
2.1
2020-10-16 CVE-2020-9959 Improper Locking vulnerability in Apple Ipad OS and Iphone OS
A lock screen issue allowed access to messages on a locked device.
local
low complexity
apple CWE-667
2.1
2020-10-16 CVE-2020-9946 Improper Locking vulnerability in Apple Ipad OS and Iphone OS
This issue was addressed with improved checks.
local
low complexity
apple CWE-667
4.6
2020-10-14 CVE-2020-0423 Improper Locking vulnerability in Google Android
In binder_release_work of binder.c, there is a possible use-after-free due to improper locking.
local
low complexity
google CWE-667
7.2
2020-10-14 CVE-2020-0420 Improper Locking vulnerability in Google Android 11.0
In setUpdatableDriverPath of GpuService.cpp, there is a possible memory corruption due to a missing permission check.
local
low complexity
google CWE-667
7.2