CWE-662: Improper Synchronization
low-riskThe product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.
Common Consequences
Detection Methods
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2020-7457 | 8.1 | 44.6% | — |
| CVE-2020-14059 | 6.5 | 4.2% | — |
| CVE-2024-7409 | 7.5 | 1.7% | — |
| CVE-2018-15555 | 9.8 | 1.2% | — |
| CVE-2016-8368 | 8.6 | 0.9% | — |
| CVE-2023-2801 | 7.5 | 0.9% | — |
| CVE-2019-17185 | 7.5 | 0.7% | — |
| CVE-2020-3471 | 6.5 | 0.6% | — |
| CVE-2024-32644 | 9.1 | 0.6% | — |
| CVE-2018-4027 | 7.5 | 0.4% | — |