CWE-909: Missing Initialization of Resource

ClassIncompleteExploit Likelihood: Medium

The product does not initialize a critical resource.

View on MITRE
Back to CWE Lookup

Extended Description

Many resources require initialization before they can be properly used. If a resource is not initialized, it could contain unpredictable or expired data, or it could be initialized to defaults that are invalid. This can have security implications when the resource is expected to have certain properties or values.

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-909 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-909, Missing Initialization of Resource, 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 Missing Initialization of Resource during Implementation

MITRE associates mitigation with Implementation, and Build and Compilation; documented detection approaches include Automated Static Analysis; recorded impacts include Read Memory, Read Application Data, and DoS: Crash, Exit, or Restart. Use these source-defined anchors to turn CWE-909 into implementation, review, and verification checks for the affected component.

CWE-909: Missing Initialization of ResourceMITRE CWE

Triage CWE-909 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-909, Missing Initialization of Resource, 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-909

Apply MITRE's full root-cause mapping guidance when using CWE-909, Missing Initialization of Resource. 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-909 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-909, Missing Initialization of Resource. 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-909: Missing Initialization of Resource?+

CWE-909: Missing Initialization of Resource is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not initialize a critical resource. Many resources require initialization before they can be properly used. If a resource is not initialized, it could contain unpredictable or expired data, or it could be initialized to defaults that are invalid. This can have security implications when the resource is expected to have certain properties or values.

What are the security consequences of Missing Initialization of Resource?+

If exploited, CWE-909 (Missing Initialization of Resource) it can compromise Confidentiality and Availability, leading to outcomes such as Read Memory, Read Application Data and DoS: Crash, Exit, or Restart.

How do you prevent or mitigate Missing Initialization of Resource?+

Recommended mitigations for CWE-909 include: Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all specified steps. Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization. Avoid race conditions (CWE-362) during initialization routines.

Which programming languages are affected by Missing Initialization of Resource?+

CWE-909 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 Missing Initialization of Resource?+

MITRE documents real CVEs mapped to CWE-909, including CVE-2020-20739 and CVE-2005-1036. 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-909 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