CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition

BaseIncompleteExploit Likelihood: Medium

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-367 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-367, Time-of-check Time-of-use (TOCTOU) Race Condition, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Address Time-of-check Time-of-use (TOCTOU) Race Condition during Implementation

MITRE associates mitigation with Implementation, and Architecture and Design; documented detection approaches include Automated Static Analysis; recorded impacts include Alter Execution Logic, Unexpected State, Modify Application Data, Modify Files or Directories, and Modify Memory. Use these source-defined anchors to turn CWE-367 into implementation, review, and verification checks for the affected component.

CWE-367: Time-of-check Time-of-use (TOCTOU) Race ConditionMITRE CWE

Triage CWE-367 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-367, Time-of-check Time-of-use (TOCTOU) Race Condition, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-367

Apply MITRE's full root-cause mapping guidance when using CWE-367, Time-of-check Time-of-use (TOCTOU) Race Condition. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-367 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-367, Time-of-check Time-of-use (TOCTOU) Race Condition. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition?+

CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

What are the security consequences of Time-of-check Time-of-use (TOCTOU) Race Condition?+

If exploited, CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) it can compromise Integrity, Other and Non-Repudiation, leading to outcomes such as Alter Execution Logic, Unexpected State, Modify Application Data, Modify Files or Directories, Modify Memory and Other.

How do you prevent or mitigate Time-of-check Time-of-use (TOCTOU) Race Condition?+

Recommended mitigations for CWE-367 include: The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check. When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement. Limit the interleaving of operations on files from multiple processes.

Which programming languages are affected by Time-of-check Time-of-use (TOCTOU) Race Condition?+

CWE-367 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Time-of-check Time-of-use (TOCTOU) Race Condition?+

MITRE documents real CVEs mapped to CWE-367, including CVE-2015-1743, CVE-2003-0813, CVE-2004-0594, CVE-2008-2958 and CVE-2008-1570. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-367 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement