Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-770 (不加限制或调节的资源分配) — Vulnerability Class 827

827 vulnerabilities classified as CWE-770 (不加限制或调节的资源分配). AI Chinese analysis included.

CWE-770 represents a critical resource management weakness where software allocates reusable resources, such as memory, file descriptors, or database connections, without enforcing limits or throttling mechanisms. This vulnerability typically arises when applications accept untrusted input or handle high-volume requests, allowing malicious actors to trigger excessive resource consumption. By rapidly requesting numerous resources, attackers can exhaust system capacity, leading to denial-of-service conditions that degrade performance or crash the entire service. To mitigate this risk, developers must implement strict quotas, rate limiting, and connection pooling strategies. Enforcing maximum thresholds for resource allocation ensures that no single user or process can monopolize system assets, thereby maintaining stability and availability even under heavy load or targeted abuse attempts.

MITRE CWE Description
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.
Common Consequences (1)
AvailabilityDoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)
When allocating resources without limits, an attacker could prevent other systems, applications, 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.
Mitigations (5)
RequirementsClearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and DesignLimit 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.
Architecture and DesignDesign 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 …
ImplementationAssume 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 input, the full range…
Architecture and DesignFor 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 server.
Examples (2)
This code allocates a socket and forks each time it receives a new connection.
sock=socket(AF_INET, SOCK_STREAM, 0); while (1) { newsock=accept(sock, ...); printf("A connection has been accepted\n"); pid = fork(); }
Bad · C
In the following example a server socket connection is used to accept a request to store data on the local file system using a specified filename. The method openSocketConnection establishes a server socket to accept requests from a client. When a client establishes a connection to this service the getNextMessage method is first used to retrieve from the socket the name of the file to store the da…
int writeDataFromSocketToFile(char *host, int port) { char filename[FILENAME_SIZE]; char buffer[BUFFER_SIZE]; int socket = openSocketConnection(host, port); if (socket < 0) { printf("Unable to open socket connection"); return(FAIL); } if (getNextMessage(socket, filename, FILENAME_SIZE) > 0) { if (openFileToWrite(filename) > 0) { while (getNextMessage(socket, buffer, BUFFER_SIZE) > 0){ if (!(writeToFile(buffer) > 0)) break; } } closeFile(); } closeSocket(socket); }
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2025-2934 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 4.3 Medium2025-10-09
CVE-2025-11362 pdfmake 安全漏洞 — pdfmake 7.5 High2025-10-07
CVE-2025-58582 Uncontrolled Resource Consumption via log file — Enterprise Analytics 5.3 Medium2025-10-06
CVE-2025-58578 Unlimited user creation by authorized users — Enterprise Analytics 3.8 Low2025-10-06
CVE-2025-11274 Open Asset Import Library Assimp Q3DLoader.cpp InternReadFile allocation of resources — Assimp 3.3 Low2025-10-05
CVE-2025-44012 Qsync Central — Qsync Central 5.8 -2025-10-03
CVE-2025-44007 Qsync Central — Qsync Central 5.8 -2025-10-03
CVE-2025-44006 Qsync Central — Qsync Central 5.8 -2025-10-03
CVE-2025-33040 Qsync Central — Qsync Central 5.8 -2025-10-03
CVE-2025-33039 Qsync Central — Qsync Central 5.8 -2025-10-03
CVE-2025-36099 IBM WebSphere Application Server denial of service — WebSphere Application Server 4.9 Medium2025-09-29
CVE-2025-8014 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 7.5 High2025-09-27
CVE-2025-11042 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 4.3 Medium2025-09-26
CVE-2025-10858 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 7.5 High2025-09-26
CVE-2025-10867 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 3.5 Low2025-09-26
CVE-2025-59418 BunnyPad Vulnerable to Buffer Overflow When Opening Files of Size 20MB or Greater — BunnyPad-SRC 5.5 Medium2025-09-22
CVE-2025-59421 Press vulnerable to email flooding to users due to lack of validation and rate limits — press--AI2025-09-18
CVE-2025-8396 Temporal OSS Server 安全漏洞 — OSS Server 7.5AIHighAI2025-09-15
CVE-2025-59375 Expat 安全漏洞 — libexpat 7.5 High2025-09-15
CVE-2025-36035 IBM PowerVM Hypervisor denial of service — PowerVM Hypervisor 6.7 Medium2025-09-14
CVE-2025-1250 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-09-12
CVE-2025-7337 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-09-12
CVE-2025-58754 Axios is vulnerable to DoS attack through lack of data size check — axios 7.5 High2025-09-12
CVE-2025-48041 SSH_FXP_OPENDIR may Lead to Exhaustion of File Handles — OTP 7.5AIHighAI2025-09-11
CVE-2025-48039 Unverified Paths can Cause Excessive Use of System Resources — OTP 7.5AIHighAI2025-09-11
CVE-2025-48038 Unverified File Handles can Cause Excessive Use of System Resources — OTP 7.5AIHighAI2025-09-11
CVE-2024-45669 IBM Security Verify Information Queue denial of service — Security Verify Information Queue 6.5 Medium2025-09-10
CVE-2025-59045 Stalwart vulnerable to Memory Exhaustion via CalDAV Event Expansion — stalwart 6.5AIMediumAI2025-09-10
CVE-2025-58446 xgrammar vulnerable to denial of service by huge enum grammar — xgrammar 7.5AIHighAI2025-09-06
CVE-2014-125127 Denial of Service (DoS) vulnerability in mikecao/flight — core 7.5 High2025-09-03

Vulnerabilities classified as CWE-770 (不加限制或调节的资源分配) represent 827 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.