CWE-908: Use of Uninitialized Resource
The product uses or accesses a resource that has not been initialized.
How it's found
Use of Uninitialized Resource is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
When a resource has not been properly initialized, the product may behave unexpectedly. This may lead to a crash or invalid memory access, but the consequences vary depending on the type of resource and how it is used within the product.
Vulnerable vs. safe
test_string = "Hello World!";char *test_string;if (i != err_val){}printf("%s", test_string);test_string = "Hello World!";char *test_string = "Done at the beginning";if (i != err_val){}printf("%s", test_string);Consequences
- 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.
- DoS: Crash, Exit, or Restart: The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend.
Mitigations
- Implementation: Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
- Implementation: Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
- Implementation: Avoid race conditions (CWE-362) during initialization routines.
- Build and Compilation: Run or compile the product with settings that generate warnings about uninitialized variables or data.
Where this fits in a TurboPentest engagement
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Frequently asked questions
What is CWE-908?
The product uses or accesses a resource that has not been initialized.
How do you find Use of Uninitialized Resource?
Use of Uninitialized Resource is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-908?
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. DoS: Crash, Exit, or Restart: The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend.
Does TurboPentest test for Use of Uninitialized Resource?
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Related CWEs
Written and reviewed by
Michel Chamberland - Founder & CEO, IntegSec
CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security
Michel has spent 20+ years on offensive security teams including IBM X-Force Red and Trustwave SpiderLabs, leading penetration tests, red team engagements, and breach response for Fortune 500 customers. He is the founder of IntegSec and the architect of TurboPentest.
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a pentest