CWE-908: Use of Uninitialized Resource

Extended Description

When a resource has not been properly initialized, the product may behave unexpectedly. This may lead to a crash or invalid memory access, but the consequences vary depending on the type of resource and how it is used within the product.

Implementation

Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.

Implementation

Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.

Implementation

Avoid race conditions (CWE-362) during initialization routines.

Build and Compilation

Run or compile the product with settings that generate warnings about uninitialized variables or data.

ConfidentialityRead MemoryRead Application Data

When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.

AvailabilityDoS: Crash, Exit, or Restart

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend.

Automated Static AnalysisEffectiveness: High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

CWE-908

Use of Uninitialized Resource

Extended Description

Potential Mitigations (4)

Common Consequences (2)

Detection Methods (1)

Modes of Introduction

Related Weaknesses

Example CVEs (13)

External Links