Non-exit on Failed Initialization

Opis

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.

Skutki

• 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.

Zapobieganie

• 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.

Przykłady podatności

• CVE-2005-1345 Product does not trigger a fatal error if missing or invalid ACLs are in a configuration file.

Słabość nadrzędna

• CWE-665 Improper Initialization
• CWE-705 Incorrect Control Flow Scoping
• CWE-636 Not Failing Securely ('Failing Open')

Kiedy powstaje

• Implementation

Dotyczy

Not Language-Specific

Uwagi

Under-studied. These issues are not frequently reported, and it is difficult to find published examples.