CWE-770: Allocation of Resources Without Limits or Throttling

BaseIncompleteExploit Likelihood: High

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.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Combine review and analysis around the CWE-770 trust boundary

MITRE identifies manual static analysis, fuzzing, automated dynamic analysis, automated static analysis as applicable detection approaches. Use them to identify allocations of memory, connections, processes, files, work items, sessions, and expensive computations that an actor can grow without a per-request, per-user, and global limit. Require a reproducible source-to-sink or policy-to-enforcement trace, record coverage gaps, and confirm suspected findings dynamically where safe; no single scanner can establish complete coverage for this weakness.

CWE-770: detection methods and operational guidanceMITRE CWE

Set enforceable quotas and budgets for every costly operation

Define maximum request sizes, records, recursion depth, execution time, memory, files, processes, connections, and third-party spend for each operation. Enforce per-request, per-identity, tenant, and global budgets on the server, apply bounded queues and timeouts, and reject excess work before allocation. Rate limiting alone is insufficient when one permitted request can consume unbounded resources.

OWASP API4:2023 Unrestricted Resource ConsumptionOWASP Foundation

Apply lessons from CVE-2020-7218 in HashiCorp Nomad

NVD maps CVE-2020-7218 to CWE-770; unauthenticated connections could consume resources without an effective limit and drive the workload orchestrator into denial of service. Use the case to cap unauthenticated connections and per-peer work, release resources on disconnect and timeout, and load-test recovery after connection floods.

CVE-2020-7218 DetailNIST National Vulnerability Database

Prioritize CWE-770 using its 2025 CWE Top 25 evidence

CWE-770 ranked #25 in the 2025 CWE Top 25 with a score of 2.54. The ranking table recorded no mapped vulnerabilities in CISA KEV for this measurement window. Use the rank to prioritize systemic prevention, detection coverage, and recurring-root-cause metrics across the portfolio, while retaining asset exposure and business impact for individual finding severity decisions.

2025 CWE Top 25 Most Dangerous Software WeaknessesMITRE CWE

Measure resource growth under sustained and oversized workloads

Establish CPU, memory, connection, queue, file, process, and downstream-cost baselines, then test oversized single requests and sustained parallel workloads in an isolated environment. Verify per-user and global quotas, bounded queues, timeouts, backpressure, cleanup after cancellation, and graceful failure. Watch for resources that continue growing after traffic stops or that let one tenant starve others.

Denial of Service Cheat SheetOWASP Foundation

Frequently Asked Questions

What is CWE-770: Allocation of Resources Without Limits or Throttling?+

CWE-770: Allocation of Resources Without Limits or Throttling is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Allocation of Resources Without Limits or Throttling?+

If exploited, CWE-770 (Allocation of Resources Without Limits or Throttling) it can compromise Availability, leading to outcomes such as DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory) and DoS: Resource Consumption (Other).

How do you prevent or mitigate Allocation of Resources Without Limits or Throttling?+

Recommended mitigations for CWE-770 include: 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. 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 should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.

How is Allocation of Resources Without Limits or Throttling detected?+

CWE-770 can be detected using Fuzzing, Automated Dynamic Analysis and Automated Static Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Allocation of Resources Without Limits or Throttling?+

CWE-770 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Allocation of Resources Without Limits or Throttling?+

MITRE documents real CVEs mapped to CWE-770, including CVE-2019-19911, CVE-2009-4017, CVE-2009-2726, CVE-2009-2540 and CVE-2009-2054. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-770 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement