CWE-770: CWE-770: Allocation of Resources Without Limits or Throttling

BaseStable

Description

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
TypeApplicable PlatformsLanguages
Platforms

Frequently Asked Questions

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

CWE-770: CWE-770: Allocation of Resources Without Limits or Throttling is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Description

What are the security consequences of CWE-770: Allocation of Resources Without Limits or Throttling?+

If exploited, CWE-770 (CWE-770: Allocation of Resources Without Limits or Throttling) it can compromise DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory) and DoS: Resource Consumption (Other), leading to outcomes such as Scope: Availability When allocating resources without limits, an attacker could prevent other systems, applications and or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed..

How do you prevent or mitigate CWE-770: 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.

Which programming languages are affected by CWE-770: Allocation of Resources Without Limits or Throttling?+

CWE-770 commonly affects Type, Applicable Platforms and Languages. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

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