- What is CWE-662?
- 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.
- What CVEs are caused by CWE-662?
- 15 recorded CVEs are attributed to CWE-662, including CVE-2024-32644, CVE-2024-7409, CVE-2023-20625.
- How do you prevent CWE-662?
- Use industry standard APIs to synchronize your code.
- How is CWE-662 detected?
- Automated Static Analysis: 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.)
- What are the consequences of CWE-662?
- Exploiting CWE-662 can lead to: Modify Application Data, Read Application Data, Alter Execution Logic.
- Is CWE-662 actively exploited?
- 15 recorded CVEs are caused by CWE-662; none are currently in CISA's KEV catalog of actively exploited flaws.
