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 826

826 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-2019-11938 Facebook Thrift 安全漏洞 — Facebook Thrift 7.5 -2020-03-10
CVE-2019-14834 dnsmasq 资源管理错误漏洞 — dnsmasq 5.3 -2020-01-07
CVE-2019-16770 Potential DOS attack in Puma — puma 5.3 Medium2019-12-05
CVE-2019-10171 Red Hat Enterprise Linux 资源管理错误漏洞 — 389-ds-base 7.5 -2019-08-02
CVE-2019-10163 PowerDNS Authoritative Server 资源管理错误漏洞 — pdns 6.5 -2019-07-30
CVE-2019-11478 SACK can cause extensive memory use via fragmented resend queue — Linux kernel 7.5 -2019-06-18
CVE-2019-3882 Linux kernel 资源管理错误漏洞 — kernel 5.5 -2019-04-24
CVE-2018-16846 Red Hat Ceph 输入验证错误漏洞 — ceph 6.5 -2019-01-15
CVE-2018-16865 systemd 缓冲区错误漏洞 — systemd 7.8 -2019-01-11
CVE-2018-16864 systemd 缓冲区错误漏洞 — systemd 7.8 -2019-01-11
CVE-2017-2587 Netpbm 资源管理错误漏洞 — netpbm 5.5 -2018-07-27
CVE-2018-3711 Fastify 安全漏洞 — fastify node module 7.5 -2018-06-07
CVE-2018-3737 sshpk 安全漏洞 — sshpk node module 7.5 -2018-06-07
CVE-2018-3738 protobufjs 安全漏洞 — protobufjs node module 5.5 -2018-06-07
CVE-2017-2613 CloudBees Jenkins 跨站请求伪造漏洞 — jenkins 4.3 -2018-05-15
CVE-2017-15124 QEMU 输入验证错误漏洞 — Qemu 7.5 -2018-01-09

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