Average request payload size reduced

firetail:average-request-payload-size-reduced

Type:

Detection

Rule Severity:

Info

The average request payload size during a given period was <= the mean average - one standard deviation of the preceding period.

The average request payload size of the API has decreased significantly, falling below the mean average minus one standard deviation of the preceding period. This indicates a drop in the amount of data being sent in requests, which could be caused by various factors such as changes in client behavior, application logic, or issues with how the API processes incoming data. A sudden and unexplained reduction in request payloads could signal potential problems with data collection, API behavior, or even an attempt to manipulate the system through smaller, less detectable requests.

Remediation

Investigate what has caused the request payloads sent to this API to decrease significantly in size.

Example Attack Scenario

An attacker may attempt to exploit the reduction in request payload size by sending smaller, more concise requests that bypass normal security or validation checks. For example, if the application typically expects large JSON payloads, an attacker may attempt to send a smaller, carefully crafted request to avoid triggering size-based detection systems or filtering rules. If the API has weak data validation or security mechanisms in place, these smaller requests could be used to perform attacks such as:

  • SQL Injection: Sending smaller queries that don’t trigger size-based filtering but still contain malicious input.
  • Data Exfiltration: Sending smaller, less suspicious payloads to slowly exfiltrate sensitive information from the server over time without raising alarms.
  • Bypassing Rate Limits: Using reduced payloads to evade payload-size-based rate limiting or security detection mechanisms.

How to Identify with Example Scenario

How to Resolve with Example Scenario

How to Identify with Example Scenario

Find the text in bold to identify issues such as these in API specifications

How to Resolve with Example Scenario

Modify the text in bold to resolve issues such as these in API specifications
References:

More findings

All Findings