Incorrect Initialization of Resource
Incorrect Initialization of Resource
CWE-1419
Short description
Extended description
This can have security implications when the associated resource is expected to have certain properties or values. Examples include a variable that determines whether a user has been authenticated or not, or a register or fuse value that determines the security state of the product.
For software, this weakness can frequently occur when implicit initialization is used, meaning the resource is not explicitly set to a specific value. For example, in C, memory is not necessarily cleared when it is allocated on the stack, and many scripting languages use a default empty, null value, or zero value when a variable is not explicitly initialized.
For hardware, this weakness frequently appears with reset values and fuses. After a product reset, hardware may initialize registers incorrectly. During different phases of a product lifecycle, fuses may be set to incorrect values. Even if fuses are set to correct values, the lines to the fuse could be broken or there might be hardware on the fuse line that alters the fuse value to be incorrect.
Best practices to prevent this CWE
Phase: Implementation
Choose the safest-possible initialization for security-related resources.
Phase: Implementation
Ensure that each resource (whether variable, memory buffer, register, etc.) is fully initialized.
Phase: Implementation
Pay close attention to complex conditionals or reset sources that affect initialization, since some paths might not perform the initialization.
Phase: Architecture and Design
Ensure that the design and architecture clearly identify what the initialization should be, and that the initialization does not have security implications.
