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.
No detection method information available for this CWE.
No examples or observed CVEs available for this CWE.
No relationship information available for this CWE.
CWE-455: CWE-455: Non-exit on Failed Initialization is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Description
If exploited, CWE-455 (CWE-455: Non-exit on Failed Initialization) it can compromise Modify Application Data and Alter Execution Logic, leading to outcomes such as Scope: Integrity and Other 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..
Recommended mitigations for CWE-455 include: 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.
CWE-455 commonly affects Languages. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
A CWE (Common Weakness Enumeration) like CWE-455 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.