← Back to sandbox
Backend & API Intermediate 2 possible tests

Resource Exhaustion

Two list endpoints — one dumps all 500 records in a single response with no limits. The other paginates correctly. Find the unbounded endpoint and measure the payload size difference.

What is this?

Resource exhaustion occurs when an API returns unlimited data in a single response — consuming excess memory, CPU, bandwidth, and browser rendering time. An attacker can trigger this repeatedly to degrade service. Missing pagination is one of the most common performance and security bugs in list endpoints.

What is hidden here

BugList All endpoint returns all 500 records in one response (~50KB+ payload)
CorrectList Paginated returns 20 records per page with total count and page metadata

List Endpoints


Records Returned
Total Records
Response Size
Records (first 5 shown)
Suggested Test Inputs
  • Click List All (No Limit) and check how many records and bytes are returned
  • Click List Paginated and note the page size and total count
  • Inspect response sizes in browser DevTools → Network tab