Vulnerabilities > Time-of-check Time-of-use (TOCTOU) Race Condition

DATE CVE VULNERABILITY TITLE RISK
2019-12-13 CVE-2019-19793 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Cyxtera Appgate SDP
In Cyxtera AppGate SDP Client 4.1.x through 4.3.x before 4.3.2 on Windows, a local or remote user from the same domain can gain privileges.
network
low complexity
cyxtera CWE-367
8.8
2019-12-03 CVE-2013-4235 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in multiple products
shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees
local
high complexity
debian fedoraproject redhat CWE-367
4.7
2019-11-25 CVE-2012-5630 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in multiple products
libuser 0.56 and 0.57 has a TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees.
6.3
2019-11-22 CVE-2015-7810 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in multiple products
libbluray MountManager class has a time-of-check time-of-use (TOCTOU) race when expanding JAR files
local
high complexity
videolan redhat fedoraproject debian CWE-367
4.7
2019-11-21 CVE-2019-10486 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Qualcomm products
Race condition due to the lack of resource lock which will be concurrently modified in the memcpy statement leads to out of bound access in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909W, MSM8939, MSM8953, MSM8996AU, MSM8998, Nicobar, QCN7605, QCS405, QCS605, QM215, SDA660, SDA845, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, SDM710, SDM845, SDX20, SDX24, SM6150, SM7150, SM8150
local
high complexity
qualcomm CWE-367
7.0
2019-11-12 CVE-2019-1380 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Microsoft products
A local elevation of privilege vulnerability exists in how splwow64.exe handles certain calls, aka 'Microsoft splwow64 Elevation of Privilege Vulnerability'.
local
low complexity
microsoft CWE-367
7.8
2019-10-31 CVE-2019-18644 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Totaldefense Anti-Virus 11.5.2.28
The malware scan function in Total Defense Anti-virus 11.5.2.28 is vulnerable to a TOCTOU bug; consequently, symbolic link attacks allow privileged files to be deleted.
network
high complexity
totaldefense CWE-367
5.9
2019-09-12 CVE-2019-11774 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Eclipse OMR
Prior to 0.1, all builds of Eclipse OMR contain a bug where the loop versioner may fail to privatize a value that is pulled out of the loop by versioning - for example if there is a condition that is moved out of the loop that reads a field we may not privatize the value of that field in the modified copy of the loop allowing the test to see one value of the field and subsequently the loop to see a modified field value without retesting the condition moved out of the loop.
network
high complexity
eclipse CWE-367
7.4
2019-08-29 CVE-2019-7307 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Apport Project Apport
Apport before versions 2.14.1-0ubuntu3.29+esm1, 2.20.1-0ubuntu2.19, 2.20.9-0ubuntu7.7, 2.20.10-0ubuntu27.1, 2.20.11-0ubuntu5 contained a TOCTTOU vulnerability when reading the users ~/.apport-ignore.xml file, which allows a local attacker to replace this file with a symlink to any other file on the system and so cause Apport to include the contents of this other file in the resulting crash report.
local
high complexity
apport-project CWE-367
7.0
2019-07-30 CVE-2019-11775 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in multiple products
All builds of Eclipse OpenJ9 prior to 0.15 contain a bug where the loop versioner may fail to privatize a value that is pulled out of the loop by versioning - for example if there is a condition that is moved out of the loop that reads a field we may not privatize the value of that field in the modified copy of the loop allowing the test to see one value of the field and subsequently the loop to see a modified field value without retesting the condition moved out of the loop.
network
high complexity
eclipse redhat CWE-367
7.4