CWE-364 Base Incomplet Medium likelihood

Signal Handler Race Condition

A signal handler race condition occurs when a program's signal handling routine is vulnerable to timing issues, allowing its state to be corrupted through asynchronous execution.

Définition

What is CWE-364?

A signal handler race condition occurs when a program's signal handling routine is vulnerable to timing issues, allowing its state to be corrupted through asynchronous execution.
Signal handlers are inherently risky because they can interrupt a program's normal execution at any point. If a handler modifies shared resources like global variables, uses non-reentrant functions (e.g., malloc, free, printf), or is registered for multiple signals, it can corrupt memory. This happens when the handler's actions clash with operations in the main code or other handlers, leading to use-after-free, double-free, or other memory corruption vulnerabilities that attackers can exploit for denial of service or code execution. To prevent these issues, design signal handlers to be minimal and reentrant. Avoid shared state, use only async-signal-safe functions, and consider blocking (masking) other signals within the handler to ensure atomicity. For resources that must be shared, implement proper synchronization or use a flag that the main program checks safely after the signal handler returns, moving complex logic out of the handler itself.
Impact réel

Real-world CVEs caused by CWE-364

  • CVE-1999-0035

    Signal handler does not disable other signal handlers, allowing it to be interrupted, causing other functionality to access files/etc. with raised privileges

  • CVE-2001-0905

    Attacker can send a signal while another signal handler is already running, leading to crash or execution with root privileges

  • CVE-2001-1349

    unsafe calls to library functions from signal handler

  • CVE-2004-0794

    SIGURG can be used to remotely interrupt signal handler; other variants exist

  • CVE-2004-2259

    SIGCHLD signal to FTP server can cause crash under heavy load while executing non-reentrant functions like malloc/free.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

  1. 1

    This code registers the same signal handler function with two different signals (CWE-831). If those signals are sent to the process, the handler creates a log message (specified in the first argument to the program) and exits.

  2. 2

    The handler function uses global state (globalVar and logMessage), and it can be called by both the SIGHUP and SIGTERM signals. An attack scenario might follow these lines:

  3. 3

    - The program begins execution, initializes logMessage, and registers the signal handlers for SIGHUP and SIGTERM. - The program begins its "normal" functionality, which is simplified as sleep(), but could be any functionality that consumes some time. - The attacker sends SIGHUP, which invokes handler (call this "SIGHUP-handler"). - SIGHUP-handler begins to execute, calling syslog(). - syslog() calls malloc(), which is non-reentrant. malloc() begins to modify metadata to manage the heap. - The attacker then sends SIGTERM. - SIGHUP-handler is interrupted, but syslog's malloc call is still executing and has not finished modifying its metadata. - The SIGTERM handler is invoked. - SIGTERM-handler records the log message using syslog(), then frees the logMessage variable.

  4. 4

    At this point, the state of the heap is uncertain, because malloc is still modifying the metadata for the heap; the metadata might be in an inconsistent state. The SIGTERM-handler call to free() is assuming that the metadata is inconsistent, possibly causing it to write data to the wrong location while managing the heap. The result is memory corruption, which could lead to a crash or even code execution, depending on the circumstances under which the code is running.

  5. 5

    Note that this is an adaptation of a classic example as originally presented by Michal Zalewski [REF-360]; the original example was shown to be exploitable for code execution.

Exemple de code vulnérable

Vulnerable C

This code registers the same signal handler function with two different signals (CWE-831). If those signals are sent to the process, the handler creates a log message (specified in the first argument to the program) and exits.

Vulnérable C 
char *logMessage;
  void handler (int sigNum) {
  		syslog(LOG_NOTICE, "%s\n", logMessage);
  		free(logMessage);
```
/* artificially increase the size of the timing window to make demonstration of this weakness easier. */* 
  		
  		sleep(10);
  		exit(0);}
  
  int main (int argc, char* argv[]) {
  ```
  		logMessage = strdup(argv[1]);
```
/* Register signal handlers. */* 
  		
  		signal(SIGHUP, handler);
  		signal(SIGTERM, handler);
  		
  		 */* artificially increase the size of the timing window to make demonstration of this weakness easier. */* 
  		
  		sleep(10);}
Exemple de code sécurisé

Secure pseudo

Sécurisé pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Liste de contrôle de prévention

How to prevent CWE-364

  • Requirements Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Architecture and Design Design signal handlers to only set flags, rather than perform complex functionality. These flags can then be checked and acted upon within the main program loop.
  • Implementation Only use reentrant functions within signal handlers. Also, use validation to ensure that state is consistent while performing asynchronous actions that affect the state of execution.
Signaux de détection

How to detect CWE-364

SAST High

Exécuter une analyse statique (SAST) sur le code source à la recherche du motif non sécurisé dans le flux de données.

DAST Moderate

Exécuter des tests de sécurité applicative dynamique (DAST) contre le point de terminaison en ligne.

Runtime Moderate

Surveiller les journaux runtime pour détecter des traces d'exception inhabituelles, des entrées malformées ou des tentatives de contournement d'autorisation.

Code review Moderate

Revue de code : signaler tout nouveau code qui traite les entrées de cette surface sans utiliser les helpers du framework validés.

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-364 et ouvre une PR de correction en moins de 60 secondes.

Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.

Obtenir une démo Essayer Plexicus gratuitement
Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-364 ?

A signal handler race condition occurs when a program's signal handling routine is vulnerable to timing issues, allowing its state to be corrupted through asynchronous execution.

Quelle est la gravité de CWE-364 ?

MITRE évalue la probabilité d'exploitation comme Moyenne — l'exploitation est réaliste mais nécessite généralement des conditions spécifiques.

Quels langages ou plateformes sont affectés par CWE-364 ?

MITRE lists the following affected platforms: C, C++.

Comment puis-je prévenir CWE-364 ?

Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Design signal handlers to only set flags, rather than perform complex functionality. These flags can then be checked and acted upon within the main program loop.

Comment Plexicus détecte et corrige CWE-364 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-364 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-364 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/364.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-364

CWE-362 Parent

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

A race condition occurs when multiple processes or threads access a shared resource simultaneously without proper coordination, creating a…

CWE-1223 Frère

Race Condition for Write-Once Attributes

This vulnerability occurs when an untrusted software component wins a race condition and writes to a hardware register before the trusted…

CWE-1298 Frère

Hardware Logic Contains Race Conditions

A hardware race condition occurs when security-critical logic circuits receive signals at slightly different times, creating temporary…

CWE-366 Frère

Race Condition within a Thread

This vulnerability occurs when two or more threads within the same application access and manipulate a shared resource (like a variable,…

CWE-367 Frère

Time-of-check Time-of-use (TOCTOU) Race Condition

This vulnerability occurs when a program verifies a resource's state (like a file's permissions or existence) but then uses it after that…

CWE-368 Frère

Context Switching Race Condition

This vulnerability occurs when an application switches between different security contexts (like privilege levels or domains) using a…

CWE-421 Frère

Race Condition During Access to Alternate Channel

A race condition occurs when an application opens a secondary communication channel intended for an authorized user, but fails to secure…

CWE-689 Frère

Permission Race Condition During Resource Copy

This vulnerability occurs when a system copies a file or resource but delays setting its final permissions until the entire copy operation…

CWE-415 Peut précéder

Double Free

A double free vulnerability occurs when a program mistakenly calls the 'free()' function twice on the same block of memory.

Ressources

Further reading

Prêt quand vous l'êtes

Arrêtez de payer par développeur.
Commencez à fermer la boucle.

Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.

Commencer gratuitement Réserver une démo