Use of a Non-reentrant Function in a Concurrent Context
CWE-663
The product calls a non-reentrant function in a concurrent context in which a competing code sequence (e.g. thread or signal handler) may have an opportunity to call the same function or otherwise influence its state.
We track 1 vulnerability of this type. 100% are rated high or critical, and the average CVSS score is 7.5.
How this weakness is prevented
- Implementation: Add synchronization to your non-reentrant function.
Latest Use of a Non-reentrant Function in a Concurrent Context vulnerabilities
- 7.5 High severity
emp3r0r: Concurrent Execution using Shared Resource with Improper Synchronization
emp3r0r is a C2 designed by Linux users for Linux environments. Prior to version 3.21.2, multiple shared maps are accessed without consistent synchronization across goroutines. Under concurrent activity, Go runtime can trigger `fatal error: concurrent map read