Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Unrestricted resource consumption means a service can have its processing capacity or its budget used up by a heavy volume of requests. It refers to a state where a site or API sets no limit on how much it accepts at once or on the resources it may use.
How does unrestricted resource consumption work?
Picture an all-you-can-eat restaurant that keeps serving dishes with no limit on people or time. The kitchen stops coping, and the cost of ingredients swells too.
OWASP's API Security Top 10 2023 explains that an API answers requests by using network bandwidth, CPU, memory, and storage. Some resources are outside services that charge per request, such as SMS, phone calls, and identity checks. The same document says that without limits, not only can the service be stopped, but operating costs and outside service charges can grow.
As examples it gives repeated calls that send password resets by SMS in bulk, and repeated downloads of a very large file that raise the cloud bill. Specific checks are on the API rate limiting page.
Why does unrestricted resource consumption matter?
On a site that uses a pay-as-you-go cloud or an outside service such as SMS authentication, it affects the bill as well as stopping the service. Whether it stops or raises the bill, the cause is the missing limit.
OWASP lists these items to check: execution timeouts, memory limits, maximum upload size, and how many operations one request may perform. The number of records returned in a list and the spending cap at outside services are in the same list. As measures, set a maximum size for input and files, and set rate limiting, a mechanism that narrows how many requests are accepted in a period, to fit business needs.
For important operations such as password recovery and one-time code confirmation, limit more strictly. For outside services, set a spending cap, or if you cannot, set a billing alert. MITRE's CWE-400 also names building a throttling mechanism into the system, recording the frequency of requests, and stopping users who exceed a threshold.
To decide where limits belong on your site, contact us.
Related terms
- Rate limiting: narrowing how many requests are accepted when many arrive in a short time.
- Vulnerability: a weakness in a program or setting that can become an entry for attack.
Next step
The points to check in an API are on the API rate limiting page. Preparation against attacks that put load on a site is in DDoS measures. The free URL check shows only what is visible from outside. For how to decide limits, contact us.
Frequently asked questions
Is unrestricted resource consumption the same as a DDoS attack?
No. A DDoS attack is a technique of putting load on a target from many devices. This flaw is the receiving side's weakness of processing even a large volume from a single machine without limit.
Could a limit get in the way of legitimate users?
If it is too low, yes. Measure normal use and start from that value with some room added. OWASP advises tuning to business needs and applying stricter limits to important operations.
Frequently asked questions
Is unrestricted resource consumption the same as a DDoS attack?
No. A DDoS attack is a technique of putting load on a target from many devices. This flaw is the receiving side's weakness of processing even a large volume from a single machine without limit.
Could a limit get in the way of legitimate users?
If it is too low, yes. Measure normal use and start from that value with some room added. OWASP advises tuning to business needs and applying stricter limits to important operations.