performing-api-rate-limiting-bypass

Featured

Tests API rate limiting implementations for bypass vulnerabilities by manipulating request headers, IP addresses, HTTP methods, API versions, and encoding schemes to circumvent request throttling controls. The tester identifies rate limit headers, determines enforcement mechanisms, and attempts bypasses including X-Forwarded-For spoofing, parameter pollution, case variation, and endpoint path manipulation. Maps to OWASP API4:2023 Unrestricted Resource Consumption. Activates for requests involving rate limit bypass, API throttling evasion, brute force protection testing, or API abuse prevention assessment.

API & Backend 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Performing API Rate Limiting Bypass ## When to Use - Testing whether API rate limiting can be circumvented to enable brute force attacks on authentication endpoints - Assessing the effectiveness of API throttling controls against credential stuffing or account enumeration - Evaluating if rate limits are enforced consistently across all API versions, methods, and encoding formats - Testing if API gateway rate limiting can be bypassed through header manipulation or IP rotation - Validating that rate limits protect against resource exhaustion and denial-of-service conditions **Do not use** without written authorization. Rate limit testing involves sending high volumes of requests that may impact service availability. ## Prerequisites - Written authorization specifying target endpoints and acceptable request volumes - Python 3.10+ with `requests`, `aiohttp`, and `asyncio` libraries - Burp Suite Professional with Turbo Intruder extension for high-speed testing - cURL for manual header manipulation testing - Knowledge of the target's CDN and WAF infrastructure (Cloudflare, AWS WAF, Akamai) - List of rate-limit bypass headers to test ## Workflow ### Step 1: Rate Limit Discovery and Baseline Identify how rate limiting is implemented: ```python import requests import time BASE_URL = "https://target-api.example.com/api/v1" headers = {"Authorization": "Bearer <token>", "Content-Type": "application/json"} # Send requests and track rate limit headers def probe_rate_limit(endp...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Listed

api-resource-consumption

Unrestricted Resource Consumption (OWASP API4) — missing rate limits, uncapped pagination, costly operations, and cost/$ amplification (SMS/email, third-party calls). Tier 2 (DoS-capable). Use to test rate-limit presence/bypass and resource exhaustion safely within RoE.

26 Updated 2 days ago
AnandJogawade
API & Backend Featured

implementing-api-rate-limiting-and-throttling

Implements API rate limiting and throttling controls using token bucket, sliding window, and fixed window algorithms to protect against brute force attacks, credential stuffing, resource exhaustion, and API abuse. The engineer configures per-user, per-IP, and per-endpoint rate limits using Redis-backed counters, API gateway plugins, or application middleware, and implements proper HTTP 429 responses with Retry-After headers. Activates for requests involving rate limiting implementation, API throttling setup, request quota management, or API abuse prevention.

36,355 Updated 2 months ago
mukul975
API & Backend Featured

exploiting-excessive-data-exposure-in-api

Tests APIs for excessive data exposure where endpoints return more data than the client application needs, relying on the frontend to filter sensitive fields. The tester intercepts API responses and analyzes them for leaked PII, internal identifiers, debug information, or sensitive business data that the UI does not display but the API transmits. This maps to OWASP API3:2023 Broken Object Property Level Authorization. Activates for requests involving API data leakage testing, excessive data exposure, response filtering bypass, or API over-fetching.

36,355 Updated 2 months ago
mukul975