CWEweakness
CWE-455 Non-exit on Failed Initialization
- Abstraction
- Class
- Structure
- Simple
- Status
- Draft
- Languages
- Not Language-Specific
- CWE version
- 5.0
Description
The product does not exit or otherwise modify its operation when security-relevant errors occur during initialization, such as when a configuration file has a format error or a hardware security module (HSM) cannot be activated, which can cause the product to execute in a less secure fashion than intended by the administrator.
Common consequences
• Integrity, Other: Modify Application Data, Alter Execution Logic — The application could be placed in an insecure state that may allow an attacker to modify sensitive data or allow unintended logic to be executed.
Potential mitigations
• [Implementation] Follow the principle of failing securely when an error occurs. The system should enter a state where it is not vulnerable and will not display sensitive error messages to a potential attacker.
Observed examples
• CVE-2005-1345: Product does not trigger a fatal error if missing or invalid ACLs are in a configuration file.
Related
Observed example · CVE (1)
- CVE-2005-1345 Squid 2.5.STABLE9 and earlier does not trigger a fatal error when it identifies missing or invalid ACLs in the http_access configuration,… vulnerability
Child of · CWE (3)
Referenced by CVE · weakness (2)
- CVE-2026-16584 Improper handling of an initialization failure in AWS API MCP Server from 0.2.13 through 1.3.46 might allow an actor to bypass the… vulnerability
- CVE-2022-4662 A flaw incorrect access control in the Linux kernel USB core subsystem was found in the way user attaches usb device. vulnerability
Referenced by CWE · has member (1)
- CWE-884 CWE Cross-section view