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

目标: 1000 元 · 已筹: 1359 元

100%

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

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

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

MITRE CWE 官方描述
CWE:CWE-400 不受控的资源消耗 (Uncontrolled Resource Consumption) 英文:该产品未正确控制有限资源的分配和维护。
常见影响 (2)
Availability DoS: 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, Other Bypass 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 Design Design 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 Design Mitigation 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 Design Ensure that protocols have specific limits of scale placed on them.
Implementation Ensure 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-86019 Part-DB 任意版本 API Base64 上传绕过漏洞 — Part-DB-server 5.3 Medium 2026-10-23
CVE-2026-86018 Part-DB 认证磁盘耗尽漏洞 — Part-DB-server 5.3 Medium 2026-10-23
CVE-2026-115390 Wasmtime 47.0.0/49.0.0 燃料计算绕过拒绝服务漏洞 — wasmtime 5.7 Medium 2026-10-22
CVE-2026-115388 Wasmtime 内存耗尽拒绝服务漏洞 — wasmtime 6.2 Medium 2026-10-22
CVE-2026-115348 Mistune 3.3.0 之前版本 DoS 漏洞 — mistune 7.5 High 2026-10-22
CVE-2026-108359 PhpSpreadsheet ODS 读取器拒绝服务漏洞 — PhpSpreadsheet 8.7 High 2026-10-22
CVE-2026-114610 FPDF2 指数级 SVG 扩展导致资源耗尽漏洞 — fpdf2 6.5 Medium 2026-10-22
CVE-2026-75507 GraphQL-core 重叠字段验证二次复杂度拒绝服务漏洞 — graphql-core 7.5 High 2026-10-22
CVE-2026-75508 GraphQL-core 拒绝服务漏洞 — graphql-core 7.5 High 2026-10-22
CVE-2026-114603 OpenTelemetry Python 无限 tracestate 解析漏洞 — opentelemetry-python 5.3 Medium 2026-10-22
CVE-2026-76290 Splunk Enterprise 未认证包下载拒绝服务漏洞 — Splunk Enterprise 7.5 High 2026-10-21
CVE-2026-76288 Splunk Enterprise 因 Content-Type 头解析导致拒绝服务漏洞 — Splunk Enterprise 7.5 High 2026-10-21
CVE-2026-96636 Pillow 多帧 seek 绕过解压炸弹保护漏洞 — Pillow 6.5 Medium 2026-10-21
CVE-2026-96640 Pillow PDF 处理共享页面树导致资源耗尽漏洞 — Pillow 8.2 High 2026-10-21
CVE-2026-96637 Pillow SpiderImagePlugin 拒绝服务漏洞 — Pillow 7.1 High 2026-10-21
CVE-2026-96638 Pillow BMP RLE 解码器内存放大拒绝服务漏洞 — Pillow 6.5 Medium 2026-10-21
CVE-2026-114144 toml-node 解析整数导致 CPU 拒绝服务漏洞 — toml-node 7.5 High 2026-10-21
CVE-2026-114138 Django REST framework 内容协商 CPU 耗尽漏洞 — django-rest-framework 7.5 High 2026-10-21
CVE-2026-111817 Apache Traffic Server 分块拖尾导致传输挂起漏洞 — Apache Traffic Server 5.3 Medium 2026-10-21
CVE-2026-111810 Apache Traffic Server 未限流日志导致拒绝服务漏洞 — Apache Traffic Server 7.5 High 2026-10-21
CVE-2026-111805 Apache Traffic Server HTTP/2 后端工作池耗尽漏洞 — Apache Traffic Server 8.6 High 2026-10-21
CVE-2026-20356 Cisco Snort 3 软件硬化发布漏洞 — Cisco Cyber Vision 7.5 High 2026-10-21
CVE-2026-113795 pypdf 多过滤器流大内存使用漏洞 — pypdf 6.0 Medium 2026-10-21
CVE-2026-113791 pypdf 解析内容流时内存耗尽漏洞 — pypdf 6.0 Medium 2026-10-21
CVE-2026-113790 pypdf 解析数组和字典时内存耗尽漏洞 — pypdf 6.0 Medium 2026-10-21
CVE-2026-113789 pypdf 表单字段检索拒绝服务漏洞 — pypdf 6.0 Medium 2026-10-21
CVE-2026-81755 Apache bRPC 单请求流过多资源耗尽漏洞 — Apache bRPC - - 2026-10-21
CVE-2026-78058 Apache bRPC HTTP/2 资源耗尽与崩溃漏洞 — Apache bRPC - - 2026-10-21
CVE-2026-61902 Apache bRPC 消息体限制不一致内存耗尽漏洞 — Apache bRPC - - 2026-10-21
CVE-2026-41114 Apache IoTDB JDBC 驱动 BigDecimal 内存耗尽漏洞 — Apache IoTDB JDBC driver - - 2026-10-21

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