Resource Exhaustion Pattern Detection
Detects patterns that lead to resource exhaustion vulnerabilities: timeout removal, iteration limit removal, resource limit increases, cleanup removal, and unbounded async operations.
Why this rule exists
Resource exhaustion attacks rely on removing the safeguards that bound resource use. Timeouts, iteration limits, and cleanup code are the first things an attacker removes. Catching their removal stops denial-of-service attacks before deployment.
Code example
try { await ProcessAsync(order); }
- catch (TimeoutException) { }
// OR
- using var conn = new SqlConnection(cs); try { await ProcessAsync(order, TimeSpan.FromSeconds(30)); }
+ catch (TimeoutException ex) { _logger.LogError(ex); throw; }Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0020": { "enabled": true, "severity": "Block" }
}
}See Configuration for the full schema.
Related rules
Resource Lifecycle
Detects disposable resources allocated without a using statement or try/finally disposal, leading to connection and handle leaks.
Error Handling Integrity
Detects swallowed exceptions (empty catch blocks) and exception handling patterns that hide failures from callers and operators.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0020_*.cs.
Eric Cogen -- Founder, GauntletCI
Twenty years in .NET production. Most of those years, the bugs that hurt me were not the ones tests caught. They were the assumptions I did not know I was making: a removed guard clause, a renamed method that still did the old thing, a catch {} that turned a page into a silent dashboard lie. GauntletCI is the checklist I wish I had run before every commit. It runs the rules I learned the hard way, so you do not have to.