CWE-666: Operation on Resource in Wrong Phase of Lifetime

Extended Description

A resource's lifecycle includes several phases: initialization, use, and release. For each phase, it is important to follow the specifications outlined for how to operate on the resource and to ensure that the resource is in the expected phase. Otherwise, if a resource is in one phase but the operation is not valid for that phase (i.e., an incorrect phase of the resource's lifetime), then this can produce resultant weaknesses. For example, using a resource before it has been fully initialized could cause corruption or incorrect data to be used.

Code Examples & CVEs

Demonstrative Examples

The following code shows a simple example of a double free vulnerability.

Double free vulnerabilities have two common (and sometimes overlapping) causes:

BadC

char* ptr = (char*)malloc (SIZE); 				   ... 				   if (abrt) { 				    					 free(ptr); 				    				   } 				   ... 				   free(ptr);

Observed CVE Examples (1)

CVE-2006-5051

Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition (CWE-362) that leads to a double free (CWE-415).

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-666 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-666, Operation on Resource in Wrong Phase of Lifetime, 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 Framework — National Institute of Standards and Technology

Address Operation on Resource in Wrong Phase of Lifetime during Architecture and Design

MITRE associates mitigation with Architecture and Design; documented detection approaches include Automated Static Analysis; recorded impacts include Other. Use these source-defined anchors to turn CWE-666 into implementation, review, and verification checks for the affected component.

CWE-666: Operation on Resource in Wrong Phase of Lifetime — MITRE CWE

Triage CWE-666 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-666, Operation on Resource in Wrong Phase of Lifetime, 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 Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-666

Apply MITRE's full root-cause mapping guidance when using CWE-666, Operation on Resource in Wrong Phase of Lifetime. 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 Guidance — MITRE CWE

Validate CWE-666 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-666, Operation on Resource in Wrong Phase of Lifetime. 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 Tips — MITRE CWE

Frequently Asked Questions

What is CWE-666: Operation on Resource in Wrong Phase of Lifetime?+

CWE-666: Operation on Resource in Wrong Phase of Lifetime is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product performs an operation on a resource at the wrong phase of the resource's lifecycle, which can lead to unexpected behaviors. A resource's lifecycle includes several phases: initialization, use, and release. For each phase, it is important to follow the specifications outlined for how to operate on the resource and to ensure that the resource is in the expected phase. Otherwise, if a resource is in one phase but the operation is not valid for that phase (i.e., an incorrect phase of the resource's lifetime), then this can produce resultant weaknesses. For example, using a resource before it has been fully initialized could cause corruption or incorrect data to be used.

What are the security consequences of Operation on Resource in Wrong Phase of Lifetime?+

If exploited, CWE-666 (Operation on Resource in Wrong Phase of Lifetime) it can compromise Other, leading to outcomes such as Other.

How do you prevent or mitigate Operation on Resource in Wrong Phase of Lifetime?+

Recommended mitigations for CWE-666 include: Follow the resource's lifecycle from creation to release.

Which programming languages are affected by Operation on Resource in Wrong Phase of Lifetime?+

CWE-666 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 Operation on Resource in Wrong Phase of Lifetime?+

MITRE documents real CVEs mapped to CWE-666, including CVE-2006-5051. 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-666 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.

CWE-666: Operation on Resource in Wrong Phase of Lifetime

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods