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-2813 HTTP Service DoS Vulnerability — AXL F BK PN TPS 7.5 High2025-07-31
CVE-2025-5253 DoS in Kron Technologies' Kron PAM — Kron PAM 6.5 Medium2025-07-25
CVE-2025-53538 Suricata's mishandling of data on HTTP2 stream 0 can lead to resource starvation — suricata 7.5 High2025-07-22
CVE-2024-38335 IBM Security QRadar Network Threat Analytics denial of service — Security QRadar Network Threat Analytics 4.5 Medium2025-07-22
CVE-2025-54121 Starlette has possible denial-of-service vector when parsing large files in multipart forms — starlette 5.3 Medium2025-07-21
CVE-2025-29606 py-libp2p 安全漏洞 — py-libp2p 4.3 Medium2025-07-14
CVE-2025-53629 cpp-httplib Unbounded Memory Allocation in Chunked/No-Length Requests Vulnerability — cpp-httplib 7.5 High2025-07-10
CVE-2025-53634 Chall-Manager's HTTP Gateway have no header check timeout leading to potential slow loris attacks — chall-manager 7.5AIHighAI2025-07-10
CVE-2025-53531 WeGIA allows Uncontrolled Resource Consumption via the fid parameter — WeGIA 7.5AIHighAI2025-07-07
CVE-2025-53530 WeGIA allows Uncontrolled Resource Consumption via the errorstr parameter — WeGIA 7.5AIHighAI2025-07-07
CVE-2025-48367 Redis DoS Vulnerability due to bad connection error handling — redis 7.5 High2025-07-07
CVE-2025-7070 IROAD Dashcam Q9 MFA Pairing Request allocation of resources — Dashcam Q9 4.3 Medium2025-07-04
CVE-2025-3279 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-06-26
CVE-2025-52889 Incus vulnerable to DoS through antispoofing nftables firewall rule bypass on bridge networks with ACLs — incus 3.4 Low2025-06-25
CVE-2025-2403 Hitachi Relion多款产品 安全漏洞 — Relion 670/650 and SAM600-IO 7.5 High2025-06-24
CVE-2025-3221 IBM InfoSphere Information Server denial of service — InfoSphere Information Server 7.5 High2025-06-21
CVE-2025-52917 Yealink YMCS RPS API 安全漏洞 — RPS 4.3 Medium2025-06-21
CVE-2025-4821 Incorrect congestion window growth by invalid ACK ranges — quiche 7.5 High2025-06-18
CVE-2025-4820 Incorrect congestion window growth by optimistic ACK — quiche 5.3 Medium2025-06-18
CVE-2025-45526 microlight.js 安全漏洞 — microlight 2.9 Low2025-06-17
CVE-2025-48988 Apache Tomcat: FileUpload large number of parts with headers DoS — Apache Tomcat 7.5 -2025-06-16
CVE-2025-1478 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-06-12
CVE-2025-1516 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-06-12
CVE-2025-5996 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2025-06-12
CVE-2025-25032 IBM Cognos Analytics denial of service — Cognos Analytics 7.5 High2025-06-11
CVE-2025-48448 Admin Audit Trail - Less critical - Denial of Service - SA-CONTRIB-2025-068 — Admin Audit Trail 8.1AIHighAI2025-06-11
CVE-2025-49140 Pion Interceptor's improper RTP padding handling allows remote crash for SFU users (DoS) — interceptor 7.5 High2025-06-09
CVE-2025-25207 Rhcl: authpolicy callbacks result in denial of service in authorino severity 5.7 Medium2025-06-09
CVE-2025-47950 CoreDNS Vulnerable to DoQ Memory Exhaustion via Stream Amplification — coredns 7.5 High2025-06-06
CVE-2025-22484 File Station 5 — File Station 5 5.0AIMediumAI2025-06-06

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