Missing Initialization of Resource

Opis

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.

Skutki

• Confidentiality

  Read Memory; Read 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.

• Availability

  DoS: Crash, Exit, or Restart

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

Zapobieganie

• Implementation

  Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all specified 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 your product with settings that generate warnings about uninitialized variables or data.

Przykłady podatności

• CVE-2020-20739 A variable that has its value set in a conditional statement is sometimes used when the conditional fails, sometimes causing data leakage
• CVE-2005-1036 Chain: Bypass of access restrictions due to improper authorization (CWE-862) of a user results from an improperly initialized (CWE-909) I/O permission bitmap

Słabość nadrzędna

• CWE-665 Improper Initialization

Może prowadzić do

• CWE-908 Use of Uninitialized Resource

Słabości podrzędne

• CWE-456 Missing Initialization of a Variable
• CWE-1271 Uninitialized Value on Reset for Registers Holding Security Settings

Kiedy powstaje

• Implementation

Dotyczy

Not Language-Specific