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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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-64529 SpiceDB's WriteRelationships fails silently if payload is too big — spicedb 8.1 -2025-11-10
CVE-2025-64509 Bugsink vulnerable to unauthenticated remote DoS via crafted Brotli input (via CPU) — bugsink 7.5 High2025-11-10
CVE-2025-64508 Bugsink vulnerable to unauthenticated remote DoS via crafted Brotli input — bugsink 7.5 High2025-11-10
CVE-2025-36008 IBM Db2 denial of service — Db2 6.5 Medium2025-11-07
CVE-2025-36136 IBM denial of service — Db2 5.1 Medium2025-11-07
CVE-2025-53409 File Station 5 — File Station 5 5.0 -2025-11-07
CVE-2025-53410 File Station 5 — File Station 5 5.0 -2025-11-07
CVE-2025-53411 File Station 5 — File Station 5 6.8 -2025-11-07
CVE-2025-53413 File Station 5 — File Station 5 5.0 -2025-11-07
CVE-2025-46556 MantisBT is Vulnerable to Denial-of-Service (DoS) attack via Excessive Note Length — mantisbt 6.5 Medium2025-11-04
CVE-2025-11374 Consul's KV endpoint is vulnerable to denial of service — Consul 6.5 Medium2025-10-28
CVE-2025-11375 Consul's event endpoint is vulnerable to denial of service — Consul 6.5 Medium2025-10-28
CVE-2025-59459 Denial-of-service (DoS) via resource consumption — TLOC100-100 5.5 Medium2025-10-27
CVE-2025-10497 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 7.5 High2025-10-27
CVE-2025-11974 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-10-27
CVE-2025-11447 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 7.5 High2025-10-27
CVE-2025-12044 Vault Vulnerable to Denial of Service Due to Rate Limit Regression — Vault 7.5 High2025-10-23
CVE-2025-62672 rplay 安全漏洞 — rplay 5.3 Medium2025-10-19
CVE-2025-62666 DoS vector through the cirrusbuilddoc query API — Mediawiki - CirrusSearch Extension 7.5AIHighAI2025-10-18
CVE-2025-11832 APIs Lack Rate Limiting — BLU-IC2 7.5AIHighAI2025-10-15
CVE-2025-59778 VELOS partition container network vulnerability — F5OS - Chassis 7.5 High2025-10-15
CVE-2025-55670 BIG-IP Next (CNF, SPK, and Kubernetes) vulnerability — BIG-IP Next SPK 6.5 Medium2025-10-15
CVE-2025-41430 BIG-IP SSL Orchestrator vulnerability — BIG-IP 7.5 High2025-10-15
CVE-2025-46706 BIG-IP iRules vulnerability — BIG-IP 7.5 High2025-10-15
CVE-2025-58474 BIG-IP Advanced WAF and ASM and NGINX App Protect DNS lookup vulnerability — BIG-IP 5.3 Medium2025-10-15
CVE-2025-55079 Missing check for thread priority — ThreadX 7.5AIHighAI2025-10-15
CVE-2025-9177 Rockwell Automation 1715 EtherNet/IP Comms Module Denial-Of-Service Vulnerability — 1715-AENTR EtherNet/IP Adapter 7.5AIHighAI2025-10-14
CVE-2025-41704 Phoenix Contact: Unauthenticated Modbus Service DoS via Crafted Function Code — QUINT4-UPS/24DC/24DC/5/EIP 5.3 Medium2025-10-14
CVE-2025-36171 IBM Aspera Faspex denial of service — Aspera Faspex 4.9 Medium2025-10-09
CVE-2025-10004 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 7.5 High2025-10-09

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