CWE-390: Detection of Error Condition Without Action
The product detects a specific error, but takes no actions to handle the error.
How it's found
Detection of Error Condition Without Action is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
Vulnerable vs. safe
//We do nothing so we just ignore the error.foo=malloc(sizeof(char)); //the next line checks to see if malloc failedif (foo==NULL) {}printf("Malloc failed to allocate memory resources");return -1;foo=malloc(sizeof(char)); //the next line checks to see if malloc failedif (foo==NULL) {}Consequences
- Varies by Context, Unexpected State, Alter Execution Logic: An attacker could utilize an ignored error condition to place the system in an unexpected state that could lead to the execution of unintended logic and could cause other unintended behavior.
Mitigations
- Implementation: Properly handle each exception. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.
- Implementation: If a function returns an error, it is important to either fix the problem and try again, alert the user that an error has happened and let the program continue, or alert the user and close and cleanup the program.
- Testing: Subject the product to extensive testing to discover some of the possible instances of where/how errors or return values are not handled. Consider testing techniques such as ad hoc, equivalence partitioning, robustness and fault tolerance, mutation, and fuzzing.
Where this fits in a TurboPentest engagement
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Frequently asked questions
What is CWE-390?
The product detects a specific error, but takes no actions to handle the error.
How do you find Detection of Error Condition Without Action?
Detection of Error Condition Without Action is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-390?
Varies by Context, Unexpected State, Alter Execution Logic: An attacker could utilize an ignored error condition to place the system in an unexpected state that could lead to the execution of unintended logic and could cause other unintended behavior.
Does TurboPentest test for Detection of Error Condition Without Action?
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Related CWEs
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a $99 pentest