Missing or Insufficient Rate Limiting

1. Executive Threat Overview

Without rate limiting, public API endpoints and login routes are vulnerable to brute-force attacks, credential stuffing, denial-of-service (DoS) attempts, and resource exhaustion.

In modern web infrastructure, missing or insufficient rate limiting represents a critical failure mode in security controls. According to A04:2021 - Insecure Design and documented under CWE-799: Improper Control of Interaction Frequency, applications failing to enforce proper controls at this layer expose their attack surface to automated crawlers, botnets, and skilled penetration testers.

When evaluating target perimeters, threat actors systematically probe for this condition using fingerprinting engines like Nmap, Nuclei, and custom fuzzing scripts. If left unresolved, this weakness can be chained with auxiliary application vulnerabilities to achieve elevated privileges, exfiltrate sensitive data, or bypass downstream security filters.

2. Technical & Business Impact

3. Exploitation Mechanics & Attack Vectors

Threat actors identify and exploit this weakness through the following attack phases:

1. Phase 1 (Reconnaissance): The attacker performs automated reconnaissance against the target domain to identify server headers, software versions, and security configurations.
2. Phase 2 (Exploitation): Utilizing known attack vectors associated with CWE-799: Improper Control of Interaction Frequency, the attacker crafts specific payloads or request patterns to trigger the vulnerability.
3. Phase 3 (Post-Exploitation & Impact): Upon successful validation, the attacker leverages the condition to compromise confidential records, manipulate user sessions, or pivot toward internal services.

4. Production Hardening & Remediation

To eliminate this vulnerability, apply the following hardened configurations to your edge web server or application codebase:

Nginx Web Server Configuration

# Recommended Nginx Hardening Configuration for Missing or Insufficient Rate Limiting:
# Apply strict security directives in the relevant server or location block
# Refer to CWE-799: Improper Control of Interaction Frequency remediation standards.

Apache 2.4 / .htaccess

# Apache 2.4 Configuration for Missing or Insufficient Rate Limiting:
# Configure Apache directives in httpd.conf or .htaccess
# Refer to A04:2021 - Insecure Design guidelines.

Application Code Implementation

Enforce request rate limits on sensitive endpoints using Redis or web application firewalls (WAFs). Return HTTP 429 Too Many Requests when limits are exceeded.

5. Verification & Testing Commands

Run the following terminal command to audit and verify that your production fixes are actively enforced:

curl -sI https://example.com/rate

6. Frequently Asked Questions