...
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
Astrée |
| uninitialized-local-read uninitialized-variable-use | Partially checked | ||||||
CodeSonar |
| LANG.MEM.UVAR | Uninitialized variable | ||||||
Compass/ROSE | Automatically detects simple violations of this rule, although it may return some false positives. It may not catch more complex violations, such as initialization within functions taking uninitialized variables as arguments. It does catch the second noncompliant code example, and can be extended to catch the first as well | ||||||||
Coverity |
| UNINIT | Implemented | ||||||
Cppcheck |
| uninitvar | Detects uninitialized variables, uninitialized pointers, uninitialized struct members, and uninitialized array elements (However, if one element is initialized, then cppcheck assumes the array is initialized.) | ||||||
GCC | 4.3.5 | Can detect some violations of this rule when the | |||||||
Klocwork |
| UNINIT.HEAP.MIGHT | |||||||
LDRA tool suite |
| 53 D, 69 D, 631 S, 652 S | Fully implemented | ||||||
Parasoft C/C++test |
| BD-BP-NOTINIT | Fully implemented | ||||||
Parasoft Insure++ | Runtime analysis | ||||||||
Polyspace Bug Finder | R2016a | Pointer not initialized before dereference Variable not initialized before use | |||||||
PRQA QA-C |
| 2961, 2962, 2963, 2966, 2967, 2968, 2971, 2972, 2973, 2976, 2977, 2978 | Fully implemented | ||||||
PRQA QA-C++ |
| 2961, 2962, 2963, 2966, 2967, 2968, 2971, 2972, 2973, 2976, 2977, 2978 | |||||||
Splint | 3.1.1 | ||||||||
RuleChecker |
| uninitialized-local-read uninitialized-variable-use | Partially checked | ||||||
PVS-Studio | 6.22 | V573, V614, V670, V679 | General analysis rule set |
Related Vulnerabilities
CVE-2009-1888 results from a violation of this rule. Some versions of SAMBA (up to 3.3.5) call a function that takes in two potentially uninitialized variables involving access rights. An attacker can exploit these coding errors to bypass the access control list and gain access to protected files [xorl 2009].
...
Key here (explains table format and definitions)
Taxonomy | Taxonomy item | Relationship |
---|---|---|
CERT C Secure Coding Standard | MSC00-C. Compile cleanly at high warning levels | Prior to 2018-01-12: CERT: Unspecified Relationship |
CERT C Secure Coding Standard | MSC01-C. Strive for logical completeness | Prior to 2018-01-12: CERT: Unspecified Relationship |
CERT C | EXP53-CPP. Do not read uninitialized memory | Prior to 2018-01-12: CERT: Unspecified Relationship |
ISO/IEC TR 24772:2013 | Initialization of Variables [LAV] | Prior to 2018-01-12: CERT: Unspecified Relationship |
ISO/IEC TS 17961 | Referencing uninitialized memory [uninitref] | Prior to 2018-01-12: CERT: Unspecified Relationship |
CWE 2.11 | CWE-456 | 2017-07-05: CERT: Exact |
CWE 2.11 | CWE-457 | 2017-07-05: CERT: Exact |
CWE 2.11 | CWE-758 | 2017-07-05: CERT: Rule subset of CWE |
CWE 2.11 | CWE-908 | 2017-07-05: CERT: Rule subset of CWE |
CERT-CWE Mapping Notes
Key here for mapping notes
...
- Read of uninitialized memory that does not represent a pointer
Bibliography
[Flake 2006] | ||
[ISO/IEC 9899:2011] | Subclause 6.7.9, "Initialization" Subclause 6.2.6.1, "General" Subclause 6.3.2.1, "Lvalues, Arrays, and Function Designators" | |
[Mercy 2006] | ||
[VU#925211] | ||
[Wang 2012] | "More Randomness or Less" | |
[xorl 2009] | "CVE-2009-1888: SAMBA ACLs Uninitialized Memory Read" |
...
...