Incorrect Synchronization
CWE-821
The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.
We track 5 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.3.
Latest Incorrect Synchronization vulnerabilities
- 8.2 High severity
Tor: Incorrect Synchronization
Tor before 0.4.9.10 did not reject a CONFLUX_LINK cell that arrives on a circuit which already has attached streams. A malicious client could send a RELAY_COMMAND_BEGIN before the CONFLUX_LINK on the same circuit, attaching an exit stream that would later end
- 9.8 Critical severity
Linux: Concurrent Execution using Shared Resource with Improper Synchronization
In the Linux kernel, the following vulnerability has been resolved: tcp: fix potential race in tcp_v6_syn_recv_sock() Code in tcp_v6_syn_recv_sock() after the call to tcp_v4_syn_recv_sock() is done too late. After tcp_v4_syn_recv_sock(), the child socket is al
- 9.1 Critical severity
lunary-ai/lunary: Incorrect Synchronization
lunary-ai/lunary is vulnerable to an authentication issue due to improper validation of email addresses during the signup process. Specifically, the server fails to treat email addresses as case insensitive, allowing the creation of multiple accounts with the
- 7.5 High severity
lunary-ai/lunary: Incorrect Synchronization
lunary-ai/lunary is vulnerable to a session reuse attack, allowing a removed user to change the organization name without proper authorization. The vulnerability stems from the lack of validation to check if a user is still part of an organization before allow
- 7.0 High severity
Red Hat Enterprise Linux 8: Improper Synchronization
A bug in QEMU could cause a guest I/O operation otherwise addressed to an arbitrary disk offset to be targeted to offset 0 instead (potentially overwriting the VM's boot code). This could be used, for example, by L2 guests with a virtual disk (vdiskL2) stored