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.
Potential Impact
Integrity
Modify Application Data
Mitigations & Prevention
Turn off dangerous handlers when performing sensitive operations.
Related Weaknesses
Taxonomy Mappings
- CERT C Secure Coding: SIG00-C — Mask signals handled by noninterruptible signal handlers
- PLOVER: — Dangerous handler not cleared/disabled during sensitive operations
Frequently Asked Questions
What is CWE-432?
CWE-432 (Dangerous Signal Handler not Disabled During Sensitive Operations) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. 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 s...
How can CWE-432 be exploited?
Attackers can exploit CWE-432 (Dangerous Signal Handler not Disabled During Sensitive Operations) to modify application data. This weakness is typically introduced during the Implementation phase of software development.
How do I prevent CWE-432?
Key mitigations include: Turn off dangerous handlers when performing sensitive operations.
What is the severity of CWE-432?
CWE-432 is classified as a Base-level weakness (Medium abstraction). Its actual severity depends on the specific context and how the weakness manifests in your application.