Backslash Vulnerability Database 
Use of Uninitialized Variable
Use of Uninitialized Variable
Use of Uninitialized Variable
CWE-457
Overtime trend (NVD)
CVSS severity (NVD, All Time)
Per technology (GHSA, All time)
- 100%-Rust
Short description
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
Extended description
In some languages such as C and C++, stack variables are not initialized by default. They generally contain junk data with the contents of stack memory before the function was invoked. An attacker can sometimes control or read these contents. In other languages or conditions, a variable that is not explicitly initialized can be given a default value that has security implications, depending on the logic of the program. The presence of an uninitialized variable can sometimes indicate a typographic error in the code.
Best practices to prevent this CWE
Phase: Implementation
Strategy: Attack Surface Reduction
Assign all variables to an initial value.
Phase: Build and Compilation
Strategy: Compilation or Build Hardening
Most compilers will complain about the use of uninitialized variables if warnings are turned on.
Phase: 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.
Phase: Requirements
The choice could be made to use a language that is not susceptible to these issues.
Phase: Architecture and Design
Mitigating technologies such as safe string libraries and container abstractions could be introduced.
