目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1325

100%

CWE-400 未加控制的资源消耗(资源穷尽) 类漏洞列表 1515

CWE-400 未加控制的资源消耗(资源穷尽) 类弱点 1515 条 CVE 漏洞汇总,含 AI 中文分析。

CWE-400 指资源消耗不受控漏洞,属于资源管理缺陷。攻击者通常通过发送大量请求或构造复杂查询,耗尽服务器 CPU、内存或带宽,导致服务拒绝。开发者应避免此类问题,需实施严格的速率限制、请求大小校验及资源配额管理,并设置合理的超时机制与异常处理逻辑,确保有限资源在预期范围内被安全分配与维护。

MITRE CWE 官方描述
CWE:CWE-400 不受控的资源消耗 (Uncontrolled Resource Consumption) 英文:该产品未正确控制有限资源的分配和维护。
常见影响 (2)
AvailabilityDoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)
If an attacker can trigger the allocation of the limited resources, but the number or size of the resources is not controlled, then the most common result is denial of service. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding envir…
Access Control, OtherBypass Protection Mechanism, Other
In some cases it may be possible to force the product to "fail open" in the event of resource exhaustion. The state of the product -- and possibly the security functionality - may then be compromised.
缓解措施 (4)
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. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perha…
Architecture and DesignMitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to preven…
Architecture and DesignEnsure that protocols have specific limits of scale placed on them.
ImplementationEnsure that all failures in resource allocation place the system into a safe posture.
代码示例 (2)
The following example demonstrates the weakness.
class Worker implements Executor { ... public void execute(Runnable r) { try { ... } catch (InterruptedException ie) { // postpone response Thread.currentThread().interrupt(); } } public Worker(Channel ch, int nworkers) { ... } protected void activate() { Runnable loop = new Runnable() { public void run() { try { for (;;) { Runnable r = ...; r.run(); } } catch (InterruptedException ie) { ... } } }; new Thread(loop).start(); } }
Bad · Java
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
CVE ID标题CVSS风险等级Published
CVE-2026-9375 urllib3 通过流式 API 中负数 max_length 绕过解压炸弹漏洞 — urllib3/urllib3--2026-06-19
CVE-2026-49293 BigInt O(n²)构造导致CPU耗尽漏洞 — js-toml 7.5 High2026-06-19
CVE-2026-48937 Node.js 22/24 HTTP/2服务器GoAway帧后持续接收数据漏洞 — node--2026-06-18
CVE-2025-53114 CometD 确认扩展内存溢出漏洞 — cometd 7.5 High2026-06-18
CVE-2025-32437 AutoGPT MediaDurationBlock拒绝服务漏洞 — AutoGPT--2026-06-18
CVE-2025-32436 AutoGPT AddAudioToVideoBlock 拒绝服务漏洞 — AutoGPT--2026-06-18
CVE-2025-32424 AutoGPT ScreenshotWebPageBlock拒绝服务漏洞 — AutoGPT--2026-06-18
CVE-2025-32422 AutoGPT FileStoreBlock 通过 StepThroughItemsBlock 导致拒绝服务漏洞 — AutoGPT--2026-06-18
CVE-2025-32392 AutoGPT LoopVideoBlock 拒绝服务漏洞 — AutoGPT--2026-06-18
CVE-2026-45357 harttle liquidjs 资源管理错误漏洞 — liquidjs 7.5 High2026-06-17
CVE-2026-44645 harttle liquidjs 资源管理错误漏洞 — liquidjs 6.5 Medium2026-06-17
CVE-2024-24769 Vantage6 资源管理错误漏洞 — vantage6--2026-06-17
CVE-2026-48990 joserfc 反序列化绕过JWS载荷大小限制漏洞 — joserfc 5.3 Medium2026-06-17
CVE-2026-48988 markdown-it smartquotes规则二次复杂度拒绝服务漏洞 — markdown-it 5.3 Medium2026-06-17
CVE-2026-9675 Node.js undici 资源管理错误漏洞 — undici 7.5 High2026-06-17
CVE-2026-12151 undici WebSocket客户端通过碎片计数绕过导致拒绝服务漏洞 — undici 7.5 High2026-06-17
CVE-2026-48779 websockets ws 资源管理错误漏洞 — ws 7.5 High2026-06-16
CVE-2026-41708 Spring Cloud Sleuth 资源管理错误漏洞 — Spring Cloud Sleuth 7.5 High2026-06-15
CVE-2026-5079 expressjs Multer 资源管理错误漏洞 — multer 7.5 High2026-06-15
CVE-2026-50011 Netty 资源管理错误漏洞 — netty 7.5 High2026-06-12
CVE-2026-48043 Netty 资源管理错误漏洞 — netty 5.3 Medium2026-06-12
CVE-2026-47244 Netty 资源管理错误漏洞 — netty 5.3 Medium2026-06-12
CVE-2026-50645 Apache CXF 资源管理错误漏洞 — Apache CXF--2026-06-12
CVE-2026-44892 Netty 配置错误漏洞 — netty 7.5 High2026-06-12
CVE-2026-45169 CyberArk PAM SH Vault 资源管理错误漏洞 — PAM SH Vault--2026-06-12
CVE-2026-44890 Netty 资源管理错误漏洞 — netty 7.5 High2026-06-11
CVE-2026-44250 Netty 资源管理错误漏洞 — netty 7.5 High2026-06-11
CVE-2026-44496 Axios 资源管理错误漏洞 — axios 7.5 High2026-06-11
CVE-2026-5497 vLLM 资源管理错误漏洞 — vllm-project/vllm--2026-06-11
CVE-2026-47734 Dulwich 资源管理错误漏洞 — dulwich 5.7 Medium2026-06-10

CWE-400(未加控制的资源消耗(资源穷尽)) 是常见的弱点类别,本平台收录该类弱点关联的 1515 条 CVE 漏洞。