Dangerous Signal Handler not Disabled During Sensitive Operations
The application uses a signal handler that shares state with other signal handlers, but it does not properly mask or prevent those signal handlers from being invoked while the original signal handler is still running.
During the execution of a signal handler, it can be interrupted by another handler when a different signal is sent. If the two handlers share state - such as global variables - then an attacker can corrupt the state by sending another signal before the first handler has completed execution.
This category identifies Software Fault Patterns (SFPs) within the Use of an Improper API cluster (SFP3).
Weaknesses in this category are related to improper management of handlers.
Weaknesses in this category are related to the improper handling of signals.
This view (slice) covers all the elements in CWE.
CWE identifiers in this view are weaknesses that do not have associated Software Fault Patterns (SFPs), as covered by the CWE-888 view. As such, they represent gaps in...
This view (slice) lists weaknesses that can be introduced during implementation.