BaseDraft

CWE-432Dangerous Signal Handler not Disabled During Sensitive Operations

Category: data-exposure

Description

The product 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.

Common consequences· 1

  • Integrity — Modify Application Data

Potential mitigations· 1

  • [Implementation]Turn off dangerous handlers when performing sensitive operations.

References

  1. https://cwe.mitre.org/data/definitions/432.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Signal Handler Race Condition
CWE
Signal Handler with Functionality that is not Asynchronous-Safe
CWE
Improper Validation of Function Hook Arguments
CWE
Use of a Non-reentrant Function in a Concurrent Context
CWE
Improper Resource Locking
CWE
Incorrect Synchronization
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.