CWE-400 là gì?
Đang phân tích dữ liệu...
CWE-400
Thống kê dữ liệu
TỔNG SỐ CVE LIÊN QUAN (365 NGÀY)574
MỨC TRỪU TƯỢNGLớp
KHẢ NĂNG KHAI THÁCCao
Số lượng lỗ hổng nằm trong CWE-400
574 lỗ hổngTăng 412,5% so với cùng kỳ
Số lượng lỗ hổng trong CISA KEV của CWE-400
1 lỗ hổng
Đặc điểm
Dữ liệu MITRE CWE chính thức
Tên gọi khác
- Resource Exhaustion
Giai đoạn hình thành
- Vận hành: The product could be operated in a system or environment with lower resource limits than expected, which might make it easier for attackers to consume all available resources.
- Cấu hình hệ thống: The product could be configured with lower resource limits than expected, which might make it easier for attackers to consume all available resources.
- Kiến trúc và thiết kế: The designer might not consider how to handle and throttle excessive resource requests, which typically requires careful planning to handle more gracefully than a crash or exit.
- Hiện thực hóa: There are at least three distinct scenarios that can commonly lead to resource exhaustion: - Lack of throttling for the number of allocated resources. - Losing all references to a resource before reaching the shutdown stage. - Not closing/returning a resource after processing. Resource exhaustion problems often occur due to an incorrect implementation of the following situations: - Error conditions and other exceptional circumstances. - Confusion over which part of the program is responsible for releasing the resource.
Hậu quả thường gặp
Dữ liệu MITRE CWE chính thức
| Tác động | Phạm vi | Diễn giải |
|---|---|---|
| Từ chối dịch vụ: sập, thoát hoặc khởi động lại, Từ chối dịch vụ: tiêu thụ tài nguyên CPU, Từ chối dịch vụ: tiêu thụ bộ nhớ, Từ chối dịch vụ: tiêu thụ tài nguyên khác | Tính sẵn sàng | 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 environment, i.e., the product may slow down, crash due to unhandled errors, or lock out legitimate users. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system. |
| Vượt qua cơ chế bảo vệ, Khác | Kiểm soát truy cập, Khác | 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. |
Biện pháp giảm thiểu rủi ro
Dữ liệu MITRE CWE chính thức
- Kiến trúc và thiết kế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, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Kiến trúc và thiết kế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 prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Kiến trúc và thiết kếEnsure that protocols have specific limits of scale placed on them.
- Hiện thực hóaEnsure that all failures in resource allocation place the system into a safe posture.
Cách phát hiện trong hệ thống
Dữ liệu MITRE CWE chính thức
| Phương pháp | Cách làm | Hiệu quả |
|---|---|---|
| Phân tích tĩnh tự động | Automated static analysis typically has limited utility in recognizing resource exhaustion problems, except for program-independent system resources such as files, sockets, and processes. For system resources, automated static analysis may be able to detect circumstances in which resources are not released after they have expired. Automated analysis of configuration files may be able to detect settings that do not specify a maximum value. Automated static analysis tools will not be appropriate for detecting exhaustion of custom resources, such as an intended security policy in which a bulletin board user is only allowed to make a limited number of posts per day. | Hạn chế |
| Phân tích động tự động | Certain automated dynamic analysis techniques may be effective in spotting resource exhaustion problems, especially with resources such as processes, memory, and connections. The technique may involve generating a large number of requests to the product within a short time frame. | Khá |
| Kiểm thử fuzzing | While fuzzing is typically geared toward finding low-level implementation bugs, it can inadvertently find resource exhaustion problems. This can occur when the fuzzer generates a large number of test cases but does not restart the targeted product in between test cases. If an individual test case produces a crash, but it does not do so reliably, then an inability to handle resource exhaustion may be the cause. | Tùy cơ hội |
Lỗ hổng điển hình
Dữ liệu MITRE CWE chính thức
Dưới đây là các lỗ hổng tiêu biểu liên quan đến CWE-400, dựa theo mức độ ưu tiên
CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.
Tìm hiểu thêm
Kiểm tra chuyên sâu cùng giải pháp quản lý rủi ro Web toàn diện
Giải pháp CyStack VulnScan liên tục phát hiện tài sản, xác minh lỗ hổng và giúp đội ngũ bảo mật ưu tiên khắc phục cho toàn bộ doanh nghiệp.
Khám phá CyStack VulnScan
