CWE-663 Use of a Non-reentrant Function in a Concurrent Context – Detailed Weakness Analysis

Explore CAPEC attack patterns referencing this CWE.

What is CWE (Common Weakness Enumeration)?

The Common Weakness Enumeration (CWE) is a community-developed list of common software and hardware weaknesses. By identifying these weaknesses, developers and security practitioners can prioritize and address potential vulnerabilities early in the development cycle. Explore our comprehensive CWE list below to better understand and mitigate common security issues.

CAPEC Patterns referencing CWE-663

Below is a list of CAPEC attack patterns associated with this CWE-663. Click on each CAPEC to learn more. The right column shows the related weaknesses (including this one).

CAPEC Related Weaknesses
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-366 Race Condition within a Thread
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
CWE-368 Context Switching Race Condition
CWE-370 Missing Check for Certificate Revocation after Initial Check
CWE-662 Improper Synchronization
CWE-663 Use of a Non-reentrant Function in a Concurrent Context
CWE-665 Improper Initialization
CWE-691 Insufficient Control Flow Management

About CWE-663: Use of a Non-reentrant Function in a Concurrent Context

CWE-663 is one of the established Common Weakness Enumerations that identifies a specific type of vulnerability in software. Detailed analysis of CWE-663 helps organizations understand the risks associated with this weakness and implement effective countermeasures.

Explore related attack patterns, best practices, and expert recommendations on this page. By understanding CWE-663, you can enhance your security posture and better protect your applications against exploitation.