Führe statische Analyse (SAST) auf der Codebasis aus und suche im Datenfluss nach dem unsicheren Muster.
CWE-1188 Base Incomplete
Initialization of a Resource with an Insecure Default
This vulnerability occurs when software uses an insecure default setting or value for a resource, assuming an administrator will change it later.
Definition
What is CWE-1188?
This vulnerability occurs when software uses an insecure default setting or value for a resource, assuming an administrator will change it later.
Developers often set open, permissive defaults to make a product easy to install and use right away. The security model relies entirely on the administrator remembering to change these defaults to a more secure configuration, which is a risky assumption.
This creates an 'out-of-the-box' vulnerability where the system is insecure from the moment it's installed. The resulting security gap remains until an admin takes action, leaving a window of exposure that attackers can easily discover and exploit.
Auswirkungen in der Praxis
Real-world CVEs caused by CWE-1188
-
insecure default variable initialization in BIOS firmware for a hardware board allows DoS
-
A generic database browser interface has a default mode that exposes a web server to the network, allowing queries to the database.
Wie Angreifer es ausnutzen
Angreiferpfad Schritt für Schritt
- 1
This code attempts to login a user using credentials from a POST request:
- 2
Because the $authorized variable is never initialized, PHP will automatically set $authorized to any value included in the POST request if register_globals is enabled. An attacker can send a POST request with an unexpected third value 'authorized' set to 'true' and gain authorized status without supplying valid credentials.
- 3
Here is a fixed version:
- 4
This code avoids the issue by initializing the $authorized variable to false and explicitly retrieving the login credentials from the $_POST variable. Regardless, register_globals should never be enabled and is disabled by default in current versions of PHP.
Verwundbares Codebeispiel
Vulnerable PHP
This code attempts to login a user using credentials from a POST request:
```
// $user and $pass automatically set from POST request*
if (login_user($user,$pass)) {
```
$authorized = true;
}
```
...*
if ($authorized) {
```
generatePage();
} Sicheres Codebeispiel
Secure PHP
Here is a fixed version:
$user = $_POST['user'];
$pass = $_POST['pass'];
$authorized = false;
if (login_user($user,$pass)) {
$authorized = true;
}
```
...* What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Präventions-Checkliste
How to prevent CWE-1188
- Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
- Implementation Validate input at trust boundaries; use allowlists, not denylists.
- Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
- Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
- Operation Monitor logs for the runtime signals listed in the next section.
Erkennungssignale
How to detect CWE-1188
Führe dynamische Application-Security-Tests gegen den Live-Endpoint aus.
Beobachte Runtime-Logs auf ungewöhnliche Exception-Traces, fehlerhafte Eingaben oder Versuche, Autorisierung zu umgehen.
Code Review: Markiere jeden neuen Code, der Eingaben von dieser Oberfläche ohne validierte Framework-Helper verarbeitet.
CWE-1188
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Häufig gestellte Fragen Was ist CWE-1188?
Wie gravierend ist CWE-1188?
Welche Sprachen oder Plattformen sind von CWE-1188 betroffen?
Wie kann ich CWE-1188 verhindern?
Wie erkennt und behebt Plexicus CWE-1188?
Wo erfahre ich mehr über CWE-1188?
Frequently asked questions
Was ist CWE-1188?
This vulnerability occurs when software uses an insecure default setting or value for a resource, assuming an administrator will change it later.
Wie gravierend ist CWE-1188?
MITRE hat für diese Schwachstelle keine Exploit-Wahrscheinlichkeit veröffentlicht. Behandle sie als mittlere Auswirkung, bis dein Threat Model anderes belegt.
Welche Sprachen oder Plattformen sind von CWE-1188 betroffen?
MITRE hat für diese CWE keine betroffenen Plattformen spezifiziert — sie kann in den meisten Anwendungs-Stacks auftreten.
Wie kann ich CWE-1188 verhindern?
Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.
Wie erkennt und behebt Plexicus CWE-1188?
Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-1188 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.
Wo erfahre ich mehr über CWE-1188?
MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/1188.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.
Verwandte Schwachstellen
Weaknesses related to CWE-1188
CWE-1419 Parent
Incorrect Initialization of Resource
This weakness occurs when a system fails to properly set up a resource during its creation, leaving it in an unstable, incorrect, or…
CWE-1051 Sibling
Initialization with Hard-Coded Network Resource Configuration Data
This vulnerability occurs when software uses fixed, hard-coded values—like IP addresses, domain names, or URLs—to identify network…
CWE-1052 Sibling
Excessive Use of Hard-Coded Literals in Initialization
This weakness occurs when software initializes variables or data structures using hard-coded values (like strings, file paths, or network…
CWE-1221 Sibling
Incorrect Register Defaults or Module Parameters
This vulnerability occurs when hardware description language (HDL) code sets insecure default values for hardware registers or…
CWE-454 Sibling
External Initialization of Trusted Variables or Data Stores
This vulnerability occurs when an application sets up its critical internal variables or storage systems using data from untrusted,…
CWE-453 Child
Insecure Default Variable Initialization
This vulnerability occurs when software sets an internal variable to an insecure or unnecessarily weak default value during…
Ressourcen
Further reading
Bereit, das Wesentliche zu validieren?
Bereit zu validieren, was zählt.
Plexicus ist Proof-Driven AppSec: validierte Funde, kontextuelles Verständnis und geprüfte Remediation — in Evidenz verankert, mit Ihnen gescoped.