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-2024-29903 Cosign vulnerable to machine-wide denial of service via malicious artifacts — cosign 4.2 Medium2024-04-10
CVE-2024-29902 Cosign vulnerable to system-wide denial of service via malicious attachments — cosign 4.2 Medium2024-04-10
CVE-2024-3382 PAN-OS: Firewall Denial of Service (DoS) via a Burst of Crafted Packets — PAN-OS 7.5 High2024-04-10
CVE-2024-26276 Siemens Parasolid 安全漏洞 — JT2Go 3.3 Low2024-04-09
CVE-2024-0081 NVIDIA NeMo 安全漏洞 — NeMo 8.6 High2024-04-05
CVE-2024-27316 Apache HTTP Server: HTTP/2 DoS by memory exhaustion on endless continuation frames — Apache HTTP Server 7.5 -2024-04-04
CVE-2024-30249 Cloudburst Network DoS in RakNet connection handling — Network 8.6 High2024-04-04
CVE-2024-27268 IBM WebSphere Application Server Liberty denial of service — WebSphere Application Server Liberty 5.9 Medium2024-04-04
CVE-2024-28871 Excessive CPU used on malformed traffic — libhtp 7.5 High2024-04-04
CVE-2024-28182 Reading unbounded number of HTTP/2 CONTINUATION frames to cause excessive CPU usage — nghttp2 5.3 Medium2024-04-04
CVE-2024-22189 QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack — quic-go 7.5 High2024-04-04
CVE-2024-28870 Suricata uses excessive resource use in malformed ssh traffic parsing — suricata 7.5 High2024-04-03
CVE-2024-29086 Arkcompiler runtime has a stack overflow svulnerability — OpenHarmony 3.3 Low2024-04-02
CVE-2024-22353 IBM WebSphere Application Server Liberty denial of service — WebSphere Application Server Liberty 5.9 Medium2024-03-31
CVE-2024-2818 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 4.3 Medium2024-03-28
CVE-2024-29025 Netty HttpPostRequestDecoder can OOM — netty 5.3 Medium2024-03-25
CVE-2023-41038 Server crash when using specific form of SET BIND statement — firebird 7.5 High2024-03-20
CVE-2020-11862 Insecure renegotiation in SSL protocol caused Denial of service attack in Privileged Account Manager — NetIQ Privileged Account Manager 8.6 High2024-03-13
CVE-2024-28102 JWCrypto vulnerable to JWT bomb Attack in `deserialize` function — jwcrypto 6.8 Medium2024-03-06
CVE-2024-23837 LibHTP unbounded folded header handling leads to denial service — libhtp 7.5 High2024-02-26
CVE-2024-23836 crafted traffic can cause denial of service — suricata 7.5 High2024-02-26
CVE-2022-34357 IBM Cognos Analytics Mobile Server denial of service — Cognos Analytics 6.5 Medium2024-02-24
CVE-2023-51393 Potential DoS due to BusFault and Assert in Ember ZNet legacy packet buffer — Ember ZNet SDK 5.3 Medium2024-02-23
CVE-2024-0563 Denial of service condition in M-Files Server — M-Files Server 4.3 Medium2024-02-23
CVE-2024-26265 Liferay Portal 和 Liferay DXP 安全漏洞 — Portal 5.0 Medium2024-02-20
CVE-2024-26308 Apache Commons Compress: OutOfMemoryError unpacking broken Pack200 file — Apache Commons Compress 7.5 -2024-02-19
CVE-2024-23979 BIG-IP SSL Client Certificate LDAP and CRLDP Authentication profiles vulnerability — BIG-IP 7.5 High2024-02-14
CVE-2024-21771 F5 AFM Signature Matching Vulnerability — BIG-IP 7.5 High2024-02-14
CVE-2024-21875 DoS attack when broadcasting billboard messages — Hacker Hotel Badge 2024 6.5 Medium2024-02-11
CVE-2024-1066 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2024-02-07

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