CWE-662: Improper Synchronization
51 CVEs have CWE-662 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 4.408%.
The 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.
Synchronization mechanisms vary widely, but they may include locking, mutexes, and semaphores.
Child of CWE-664: Improper Control of a Resource Through its Lifetime
Mitigations
- Implementation: Use industry standard APIs to synchronize your code.
Observed examples
- CVE-2021-1782: Chain: improper locking (CWE-667) leads to race condition (CWE-362), as exploited in the wild per CISA KEV.
- CVE-2009-0935: Attacker provides invalid address to a memory-reading function, causing a mutex to be unlocked twice
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-662'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-662'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).