All rules
GCI0020BlockSecurity

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

Triggers the rule
  try { await ProcessAsync(order); }
- catch (TimeoutException) { }
  // OR
- using var conn = new SqlConnection(cs);
Passes the rule
  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

Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0020_*.cs.

About the author

Eric Cogen -- Founder, GauntletCI

Twenty years as a senior technical consultant building and modernizing enterprise platforms across .NET, AWS, serverless, microservices, and AI-driven systems.