CWE-413: Improper Resource Locking
low-riskThe product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.
Abstraction: Base
Common Consequences
Integrity
→
Modify Application Data
Detection Methods
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.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2026-32748 | 7.5 | 1.3% | — |
| CVE-2019-17102 | 8.3 | 0.3% | — |
| CVE-2022-20678 | 8.6 | 0.3% | — |
| CVE-2022-49737 | 7.7 | 0.2% | — |
| CVE-2023-28649 | 8.6 | 0.1% | — |
| CVE-2023-32253 | 5.9 | 0.1% | — |
| CVE-2025-3450 | 10.0 | 0.1% | — |
| CVE-2025-69198 | 6.5 | 0.0% | — |
| CVE-2019-8998 | 7.8 | 0.0% | — |
| CVE-2023-2269 | 4.4 | 0.0% | — |
0
/ 100
low-risk
Active Threat
0/50 · Minimal
Exploit Availability
0/50 · Minimal