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-2026-29612 OpenClaw < 2026.2.14 - Denial of Service via Large Base64 Media File Decoding — OpenClaw 5.5 Medium2026-03-05
CVE-2026-29609 OpenClaw < 2026.2.14 - Denial of Service via Unbounded URL-backed Media Fetch — OpenClaw 7.5 High2026-03-05
CVE-2026-28478 OpenClaw < 2026.2.13 - Denial of Service via Unbounded Webhook Request Body Buffering — OpenClaw 7.5 High2026-03-05
CVE-2026-28452 OpenClaw < 2026.2.14 - Denial of Service via Unguarded Archive Extraction in extractArchive — OpenClaw 5.5 Medium2026-03-05
CVE-2026-28394 OpenClaw < 2026.2.15 - Denial of Service via Unbounded Response Parsing in web_fetch Tool — OpenClaw 6.5 Medium2026-03-05
CVE-2026-28342 OliveTin: Unauthenticated Denial of Service via Memory Exhaustion in PasswordHash API Endpoint — OliveTin 7.5 High2026-03-05
CVE-2026-26998 Traefik: unbounded io.ReadAll on auth server response body causes OOM denial of service(DOS) — traefik 4.4 Medium2026-03-05
CVE-2026-20103 Cisco Secure Firewall Adaptive Security Appliance和Cisco Secure Firewall Threat Defense 安全漏洞 — Cisco Secure Firewall Adaptive Security Appliance (ASA) Software 8.6 High2026-03-04
CVE-2026-27932 joserfc PBES2 p2c Unbounded Iteration Count enables Denial of Service (DoS) — joserfc 7.5 High2026-03-03
CVE-2026-27601 Underscore.js has unlimited recursion in _.flatten and _.isEqual, potential for DoS attack — underscore 7.5AIHighAI2026-03-03
CVE-2026-27887 Spin has memory leaks in various WIT interfaces — spin 8.6AIHighAI2026-02-26
CVE-2026-1662 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 7.5 High2026-02-25
CVE-2026-1725 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 5.3 Medium2026-02-25
CVE-2026-2845 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2026-02-25
CVE-2025-3525 Allocation of Resources Without Limits or Throttling in GitLab — GitLab 6.5 Medium2026-02-25
CVE-2026-27695 zae-limiter: DynamoDB hot partition throttling enables per-entity Denial of Service — zae-limiter 4.3 Medium2026-02-25
CVE-2026-27572 Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance — wasmtime 7.5 -2026-02-24
CVE-2026-25985 Memory allocation with excessive without limits in the internal SVG decoder — ImageMagick 7.5 High2026-02-24
CVE-2026-27729 Astro has memory exhaustion DoS due to missing request body size limit in Server Actions — astro 5.9 Medium2026-02-24
CVE-2026-27026 pypdf possibly has long runtimes for malformed FlateDecode streams — pypdf 6.5AIMediumAI2026-02-20
CVE-2026-26313 Go Ethereum affected by DoS via malicious p2p message — go-ethereum 7.5 -2026-02-19
CVE-2026-26312 Stalwart Mail Server has Out-of-Memory Denial of Service via Malformed Nested MIME Messages — stalwart 6.5 Medium2026-02-19
CVE-2019-25350 XMedia Recode 3.4.8.6 - '.m3u' Denial Of Service — XMedia Recode 7.5 High2026-02-18
CVE-2025-14876 Qemu-kvm: unbounded allocation in virtio-crypto 5.5 Medium2026-02-18
CVE-2019-25342 Centova Cast 3.2.12 - Denial of Service — Centova Cast 7.5 High2026-02-12
CVE-2026-26076 ntpd-rs affected by excessive CPU load from malformed packets — ntpd-rs 5.3AIMediumAI2026-02-12
CVE-2026-21434 webtransport-go affected by Memory Exhaustion Attack due to Missing Length Check in WT_CLOSE_SESSION Capsule — webtransport-go 5.3 Medium2026-02-12
CVE-2025-54155 File Station 5 — File Station 5 6.8AIMediumAI2026-02-11
CVE-2025-54161 File Station 5 — File Station 5 6.8AIMediumAI2026-02-11
CVE-2025-57708 Qsync Central — Qsync Central 5.8AIMediumAI2026-02-11

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