| CWE-455 |
The software 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, which can cause the software to execute in a less secure fashion than intended by the administrator. |
| CWE-456 |
The software does not initialize critical variables, which causes the execution environment to use unexpected values. |
| CWE-457 |
The code uses a variable that has not been initialized, leading to unpredictable or unintended results. |
| CWE-458 |
This weakness has been deprecated because its name and description did not match. The description duplicated CWE-454, while the name suggested a more abstract initialization problem. Please refer to CWE-665 for the more abstract problem. |
| CWE-459 |
The software does not properly "clean up" and remove temporary or supporting resources after they have been used. |
| CWE-46 |
A software system that accepts path input in the form of trailing space ('filedir ') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files. |
| CWE-460 |
The product does not clean up its state or incorrectly cleans up its state when an exception is thrown, leading to unexpected state or control flow. |
| CWE-462 |
Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error. |
| CWE-463 |
The accidental deletion of a data-structure sentinel can cause serious programming logic problems. |
| CWE-464 |
The accidental addition of a data-structure sentinel can cause serious programming logic problems. |
