CWE-1188: Initialization of a Resource with an Insecure Default
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
How it's found
Initialization of a Resource with an Insecure Default 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.
Vulnerable vs. safe
// $user and $pass automatically set from POST request
...$authorized = true;
generatePage();if (login_user($user,$pass)) {}if ($authorized) {}$authorized = true;...$user = $_POST['user'];$pass = $_POST['pass'];$authorized = false;if (login_user($user,$pass)) {}Consequences
- Varies by Context: The impact of insecure defaults varies widely depending on the functionality that the product controls.
How TurboPentest tests for this (white-box)
This weakness (Initialization of a Resource with an Insecure Default) is caught by white-box static analysis when you connect a GitHub repo: IntegSec's Opengrep SAST rule pack carries 5 rules for it, flagging the issue directly in your source code as part of the pentest.
Frequently asked questions
What is CWE-1188?
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
How do you find Initialization of a Resource with an Insecure Default?
Initialization of a Resource with an Insecure Default 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-1188?
Varies by Context: The impact of insecure defaults varies widely depending on the functionality that the product controls.
Does TurboPentest test for Initialization of a Resource with an Insecure Default?
This weakness (Initialization of a Resource with an Insecure Default) is caught by white-box static analysis when you connect a GitHub repo: IntegSec's Opengrep SAST rule pack carries 5 rules for it, flagging the issue directly in your source code as part of the pentest.
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