CWE-457 Use of Uninitialized Variable

The code uses a variable that has not been initialized, leading to unpredictable or unintended results.

• Confidentiality, Integrity, Availability, Other: Varies by Context, Read Application Data — Uninitialized variables usually contain junk, which can not be trusted for consistency. Depending on the context, uninitialized variables could lead to denial of service conditions, or modify control flow in unexpected ways. They could also contain sensitive information that could be leaked if the variable is used in output. In some cases, an attacker can "pre-initialize" the variable using previous actions - i.e., control the contents of the variable - which might enable code execution. • Availability: Alter Execution Logic, Unexpected State — This can cause a race condition if a lock variable check passes when it should not. • Authorization, Other: Varies by Context — Strings that are not initialized are especially dangerous, since many functions expect a null at the end -- and only at the end -- of a string.

• [Implementation] Ensure that critical variables are initialized before first use [REF-1485]. • [Build and Compilation] Most compilers will complain about the use of uninitialized variables if warnings are turned on. • [Implementation, Operation] When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name. • [Requirements] Choose a language that is not susceptible to these issues. • [Architecture and Design] Mitigating technologies such as safe string libraries and container abstractions could be introduced.

• Fuzzing: Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues. • 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-2019-15900: Chain: sscanf() call is used to check if a username and group exists, but the return value of sscanf() call is not checked (CWE-252), causing an uninitialized variable to be checked (CWE-457), returning success to allow authorization bypass for executing a privileged (CWE-863). • CVE-2008-3688: Chain: A denial of service may be caused by an uninitialized variable (CWE-457) allowing an infinite loop (CWE-835) resulting from a connection to an unresponsive server. • CVE-2008-0081: Uninitialized variable leads to code execution in popular desktop application. • CVE-2007-4682: Crafted input triggers dereference of an uninitialized object pointer. • CVE-2007-3468: Crafted audio file triggers crash when an uninitialized variable is used. • CVE-2007-2728: Uninitialized random seed variable used.