CWE-665 Improper Initialization

The product does not initialize or incorrectly initializes a resource.

• Other: Varies by Context — The resource might be left in an unexpected state when it is accessed or used. • 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. • Access Control: Bypass Protection Mechanism — If security-critical decisions rely on a variable having a "0" or equivalent value, and the programming language performs this initialization on behalf of the programmer, then a bypass of security may occur. • Availability: DoS: Crash, Exit, or Restart — The uninitialized data may contain values that cause program flow to change in ways that the programmer did not intend. For example, if an uninitialized variable is used as an array index in C, then its previous contents may produce an index that is outside the range of the array, possibly causing a crash or an exit in other environments.

• [Requirements] Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable's type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed. • [Architecture and Design] Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values. • [Implementation] Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage. • [Implementation] Pay close attention to complex conditionals that affect initialization, since some conditions 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.

• Automated Dynamic Analysis: This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results. Initialization problems may be detected with a stress-test by calling the software simultaneously from a large number of threads or processes, and look for evidence of any unexpected behavior. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results. • Manual Dynamic Analysis: Identify error conditions that are not likely to occur during normal usage and trigger them. For example, run the program under low memory conditions, run with insufficient privileges or permissions, interrupt a transaction before it is completed, or disable connectivity to basic network services such as DNS. Monitor the software for any unexpected behavior. If you trigger an unhandled exception or similar error that was discovered and handled by the application's environment, it may still indicate unexpected conditions that were not handled by the application itself. • Automated Static Analysis: 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.)

• CVE-2001-1471: Chain: an invalid value prevents a library file from being included, skipping initialization of key variables, leading to resultant eval injection. • CVE-2008-3637: Improper error checking in protection mechanism produces an uninitialized variable, allowing security bypass and code execution. • CVE-2008-4197: Use of uninitialized memory may allow code execution. • CVE-2008-2934: Free of an uninitialized pointer leads to crash and possible code execution. • CVE-2007-3749: OS kernel does not reset a port when starting a setuid program, allowing local users to access the port and gain privileges. • CVE-2008-0063: Product does not clear memory contents when generating an error message, leading to information leak. • CVE-2008-0062: Lack of initialization triggers NULL pointer dereference or double-free. • CVE-2008-0081: Uninitialized variable leads to code execution in popular desktop application. • CVE-2008-3688: Chain: Uninitialized variable leads to infinite loop. • CVE-2008-3475: Chain: Improper initialization leads to memory corruption. • CVE-2008-5021: Composite: race condition (CWE-362) allows attacker to modify an object while it is still being initialized, causing software to access uninitialized memory (CWE-908). • 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 • CVE-2008-3597: Chain: game server can access player data structures before initialization has happened leading to NULL dereference • CVE-2009-2692: Chain: Use of an unimplemented network socket operation pointing to an uninitialized handler function (CWE-456) causes a crash because of a null pointer dereference (CWE-476). • CVE-2009-0949: Chain: improper initialization of memory can lead to NULL dereference • CVE-2009-3620: Chain: some unprivileged ioctls do not verify that a structure has been initialized before invocation, leading to NULL dereference