Security weaknessCWE Top 25 · #25
CWE-770 Missing resource limits
Your site lets one visitor use unlimited requests, memory or storage, which can slow or stop it for everyone.
- Senior security engineers
- 540+ projects delivered
- Reply within one business day
Quick answer
What is CWE-770?
Allocation of Resources Without Limits or Throttling: The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Business impact
What CWE-770 could cost your business
MITRE documents what this weakness can do. Here is what that means for a website, store or app.
Availability
Downtime and lost sales
Crashes, slowdowns or exhausted resources can take your site, store or app offline.
- DoS: Resource Consumption (CPU)
- DoS: Resource Consumption (Memory)
- DoS: Resource Consumption (Other)
In plain English
What Missing resource limits means for your business
- 540+projects delivered
- 9+years in business
- 23+certified experts
A senior engineer replies within one business day.
Every request your site handles uses something finite: processor time, memory, database connections, disk space, email sends or paid API calls. This weakness means the software hands out those resources without any cap on how many a single user can take or how large each one can be. Someone sends requests very quickly, uploads huge files or asks for enormous result sets, and the system tries to serve it all.
The usual result is a denial of service, meaning the site becomes slow or unavailable for real customers. That costs sales and support time. On usage-billed cloud hosting or metered services such as SMS, email and AI APIs, it can also produce an unexpectedly large bill. It does not always take an attacker. A badly behaved bot, a buggy integration or a sudden traffic spike can trigger the same failure.
Where it shows up
- Login, signup, search and contact form endpoints that accept unlimited requests per visitor, so automated traffic can flood the server or your inbox.
- File upload features with no cap on file size, file count or total storage, which can fill the disk and stop the site.
- API and GraphQL endpoints that let a caller request any page size or deeply nested data, forcing heavy database work per request.
- Features that trigger paid or slow work on demand, such as sending SMS codes, generating PDFs, resizing images or calling an AI service.
Free security check
Is CWE-770 hiding in your site?
A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.
Official definition
How MITRE defines CWE-770
Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Fix it
How to fix Missing resource limits
Practical steps in priority order. Share them with your developer or agency.
Rate limit requests per client
Apply request limits per IP address, account and API key at the CDN, web application firewall or gateway. Use tighter limits on login, signup, search and other costly endpoints, and return a clear retry-later response.
Cap sizes on everything accepted
Set maximum request body size, upload size, file count, field length and JSON depth at both the web server and the application. Reject oversized input early, before it is read into memory.
Bound queries and add timeouts
Enforce pagination with a maximum page size, limit GraphQL query depth and complexity, and set timeouts on database queries and outbound calls. Size connection pools so one slow dependency cannot exhaust the server.
Set quotas and queue heavy work
Give each user or tenant a quota for storage, messages and expensive operations. Move slow tasks such as exports and image processing to a background queue with a fixed number of workers.
Monitor usage and cap spending
Track request rates, error rates, memory, disk and queue length, and alert on unusual growth. Set budget alerts, and spending caps where available, with your cloud, SMS, email and AI providers.
Signs you may be affected
- The site slows down or goes offline during bursts of traffic from a few addresses.
- Hosting, SMS, email or API bills jump without a matching rise in real customers.
- Disk space, memory or database connections run out and a restart only helps briefly.
Questions to ask your developer
- Which endpoints have rate limits, and what are the limits per user?
- What is the maximum upload size and page size our server will accept?
- Do we have spending alerts on cloud, SMS, email and AI services?
Prevention
What MITRE recommends, phase by phase
Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.
- 01
Requirements
- Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
- 02
Architecture and Design
- Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
- Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place, and it will help the administrator to identify who is committing the abuse. The login application.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the.
Show 4 more recommendations
- Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, typically by using increasing time delays uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an.
- Ensure that protocols have specific limits of scale placed on them.
- If the program must fail, ensure that it fails gracefully (fails closed). There may be a temptation to simply let the program fail poorly in cases such as low memory conditions, but an attacker may be able to assert control before the software has fully exited. Alternately, an uncontrolled failure could cause cascading problems with other downstream components; for example, the.
- Use quotas or other resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems. When the current levels get.
- 03
Implementation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of.
Detection and evidence
How CWE-770 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
How it is detected
- Manual Static AnalysisManual static analysis can be useful for finding this weakness, but it might not achieve desired code coverage within limited time constraints. If denial-of-service is not considered a significant risk, or if there is strong emphasis on consequences such as code execution, then manual analysis may.
- FuzzingWhile fuzzing is typically geared toward finding low-level implementation bugs, it can inadvertently find uncontrolled resource allocation problems. This can occur when the fuzzer generates a large number of test cases but does not restart the targeted product in between test cases. If an individual.
- Automated Dynamic AnalysisCertain automated dynamic analysis techniques may be effective in producing side effects of uncontrolled resource allocation problems, especially with resources such as processes, memory, and connections. The technique may involve generating a large number of requests to the product within a short.
- Automated Static AnalysisSpecialized configuration or tuning may be required to train automated tools to recognize this weakness. Automated static analysis typically has limited utility in recognizing unlimited allocation problems, except for the missing release of program-independent system resources such as files.
Real vulnerabilities it caused
- CVE-2019-19911Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190).
- CVE-2009-4017Language interpreter does not restrict the number of temporary files being created when handling a MIME request with a large number of parts..
- CVE-2009-2726Driver does not use a maximum width when invoking sscanf style functions, causing stack consumption.
- CVE-2009-2540Large integer value for a length property in an object causes a large amount of memory allocation.
- CVE-2009-2054Product allows exhaustion of file descriptors when processing a large number of TCP packets.
- CVE-2008-5180Communication product allows memory consumption with a large number of SIP requests, which cause many sessions to be created.
How we fix it
From finding to fixed: how Codefreex closes CWE-770
Scan and confirm
We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.
Fix at the source
We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.
Verify the fix
We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.
Keep it fixed
Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.
Website SecurityPenetration TestingMalware Removal & Hack RepairWordPress Maintenance
Related weaknesses
Weaknesses related to CWE-770
FAQ
CWE-770: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
How serious is missing rate limiting for a business?
The main risk is downtime. If one client can exhaust your server, your store or app stops working for paying customers until someone intervenes. There can be direct costs too, such as cloud overage charges or bills for messages you did not mean to send. MITRE rates the likelihood of exploitation as high and notes that it can be easy to do.
How do I prevent resource exhaustion?
Decide the reasonable maximum for each resource, then enforce it. Limit request rates per client, cap upload and payload sizes, require pagination, and set timeouts on slow operations. Put heavy jobs in a queue. Add monitoring and budget alerts so you learn about unusual usage from a notification, not from an outage or an invoice.
Will a CDN or firewall solve this on its own?
It helps, but it is not the whole answer. A CDN or web application firewall can absorb floods and apply general rate limits at the edge. It cannot know that one valid request asks your database for an enormous number of rows or uploads a file too large to process. You still need limits inside the application itself.
What is CWE-770?
CWE-770, “Allocation of Resources Without Limits or Throttling”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How serious is CWE-770?
MITRE rates the likelihood of exploit as High. It can affect availability, with impacts such as dos: resource consumption (cpu), dos: resource consumption (memory), dos: resource consumption (other). It ranks number 25 on the 2025 CWE Top 25 Most Dangerous Software Weaknesses. The real risk depends on where the weakness sits and what data or functions it exposes.
How do you prevent CWE-770?
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits. Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Can Codefreex check my site for CWE-770?
Yes. A senior engineer reviews your site, store or app for CWE-770 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.
Free security check
Find out if CWE-770 affects your site
Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.
- A senior strategist reviews your request, not a sales bot
- Clear scope, timeline and estimate within one business day
- Free 30-minute discovery call, no obligation
- NDA available on request
- Emailhello@codefreex.com
- CallUSA +1 (209) 375-3475 · India +91 790 3375 530
- Prefer to talk?Book a 30-minute call
Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.