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-14299 Improper Content-Length Validation in HTTPS Requests on Tapo C200 — Tapo C200 V3 5.7AIMediumAI2025-12-20
CVE-2025-68390 Elasticsearch Allocation of Resources Without Limits or Throttling — Elasticsearch 4.9 Medium2025-12-18
CVE-2025-68389 Kibana Allocation of Resources Without Limits or Throttling — Kibana 6.5 Medium2025-12-18
CVE-2025-68384 Elasticsearch Allocation of Resources Without Limits or Throttling — Elasticsearch 6.5 Medium2025-12-18
CVE-2025-68388 Elastic Packetbeat 安全漏洞 — Packetbeat 5.3 Medium2025-12-18
CVE-2025-14466 Güralp Systems Fortimus Series, Minimus Series, and Certimus Series have an Allocation of Resources Without Limits or Throttling vulnerability — Fortimus Series 5.3 Medium2025-12-16
CVE-2025-68156 Expr has Denial of Service via Unbounded Recursion in Builtin Functions — expr 7.5 High2025-12-16
CVE-2025-64702 quic-go HTTP/3 QPACK Header Expansion DoS — quic-go 5.3 Medium2025-12-11
CVE-2025-4097 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-12-11
CVE-2025-12562 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 7.5 High2025-12-11
CVE-2025-14157 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-12-11
CVE-2025-66473 XWiki's REST APIs don't enforce any limits, leading to unavailability and OOM in large wikis — xwiki-platform 7.5AIHighAI2025-12-10
CVE-2025-9368 432ES-IG3 Series A Denial-of-Service Vulnerability — 432ES-IG3 Series A 7.5AIHighAI2025-12-09
CVE-2025-41693 Authenticated Denial-of-Service via SSH — FL SWITCH 2005 4.3 Medium2025-12-09
CVE-2025-41694 Authenticated Denial-of-Service via Webshell — FL SWITCH 2005 6.5 Medium2025-12-09
CVE-2025-36140 IBM watsonx.data Denial of Service — watsonx.data 6.5 Medium2025-12-08
CVE-2025-66418 urllib3 allows an unbounded number of links in the decompression chain — urllib3 7.5 -2025-12-05
CVE-2025-12385 Improper validation of <img> tag size in Text component parser — Qt 7.5AIHighAI2025-12-03
CVE-2025-13751 OpenVPN 安全漏洞 — OpenVPN 5.5AIMediumAI2025-12-03
CVE-2025-65113 ClipBucket v5 Unauthenticated Object Flagging Vulnerability — clipbucket-v5 6.5 Medium2025-11-29
CVE-2025-64334 Suricata is vulnerable to unbounded memory growth for decompression — suricata 7.5 High2025-11-26
CVE-2025-7449 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-11-26
CVE-2025-12571 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 7.5 High2025-11-26
CVE-2025-65942 VictoriaMetrics Snappy Decoder DoS Vulnerability is Causing OOM — VictoriaMetrics 2.7 Low2025-11-25
CVE-2025-62426 vLLM vulnerable to DoS via large Chat Completion or Tokenization requests with specially crafted `chat_template_kwargs` — vllm 6.5 Medium2025-11-21
CVE-2025-11243 Allocation of Resources Without Limits or Throttling in Shelly Pro 4PM — Pro 4PM 7.5AIHighAI2025-11-19
CVE-2025-65015 joserfc has Possible Uncontrolled Resource Consumption Vulnerability Triggered by Logging Arbitrarily Large JWT Token Payloads — joserfc 7.5AIHighAI2025-11-18
CVE-2025-13165 Digiwin|EasyFlow GP - Denial of service — EasyFlow GP 7.5 High2025-11-17
CVE-2025-59089 Python-kdcproxy: remote dos via unbounded tcp upstream buffering — kdcproxy 5.9 Medium2025-11-12
CVE-2025-12748 Libvirt: denial of service in xml parsing 5.5 Medium2025-11-11

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