ClassDraftTop 25 #24
CWE-400Uncontrolled Resource Consumption
Category: logic
Description
The product does not properly control the allocation and maintenance of a limited resource.
Common consequences· 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 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.
- Access Control / Other — Bypass Protection Mechanism, OtherIn 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.
Potential mitigations· 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, 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.
- [Architecture and Design]
- [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.
Related CAPEC attack patterns· 3
References
Exploits (incoming)3
| Type | Target | Confidence | Tier |
|---|---|---|---|
| AttackPattern | Regular Expression Exponential Blowupcapec-492 | 100% | live |
| AttackPattern | XML Ping of the Deathcapec-147 | 100% | live |
| AttackPattern | Sustained Client Engagementcapec-227 | 100% | live |
Compliance frameworks addressing this (incoming)9
| Type | Target | Confidence | Tier |
|---|---|---|---|
| ComplianceControl | nist_csf-rc | 100% | live |
| ComplianceControl | tiber_eu-closure | 100% | live |
| ComplianceControl | dora-art11 | 100% | live |
| ComplianceControl | owasp_top10-a04 | 100% | live |
| ComplianceControl | owasp_api_top10-api04 | 100% | live |
| ComplianceControl | gdpr-art32 | 100% | live |
| ComplianceControl | dora-art7 | 100% | live |
| ComplianceControl | nis2-art21c | 100% | live |
| ComplianceControl | dora-art10 | 100% | live |
(incoming)35
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2025-10470cve-2025-10470 | 0% | live |
| Vulnerability | CVE-2025-10932cve-2025-10932 | 0% | live |
| Vulnerability | CVE-2025-20162cve-2025-20162 | 0% | live |
| Vulnerability | CVE-2025-21547cve-2025-21547 | 0% | live |
| Vulnerability | CVE-2025-24190cve-2025-24190 | 0% | live |
| Vulnerability | CVE-2025-24211cve-2025-24211 | 0% | live |
| Vulnerability | CVE-2025-24247cve-2025-24247 | 0% | live |
| Vulnerability | CVE-2025-24260cve-2025-24260 | 0% | live |
| Vulnerability | CVE-2025-24264cve-2025-24264 | 0% | live |
| Vulnerability | CVE-2025-24269cve-2025-24269 | 0% | live |
| Vulnerability | CVE-2025-25205cve-2025-25205 | 0% | live |
| Vulnerability | CVE-2025-43193cve-2025-43193 | 0% | live |
| Vulnerability | CVE-2025-48609cve-2025-48609 | 0% | live |
| Vulnerability | CVE-2025-53371cve-2025-53371 | 0% | live |
| Vulnerability | CVE-2025-58349cve-2025-58349 | 0% | live |
| Vulnerability | CVE-2025-61303cve-2025-61303 | 0% | live |
| Vulnerability | CVE-2025-6297cve-2025-6297 | 0% | live |
| Vulnerability | CVE-2025-65781cve-2025-65781 | 0% | live |
| Vulnerability | CVE-2025-70327cve-2025-70327 | 0% | live |
| Vulnerability | CVE-2025-7070cve-2025-7070 | 0% | live |
| Vulnerability | CVE-2026-20084cve-2026-20084 | 0% | live |
| Vulnerability | CVE-2026-21485cve-2026-21485 | 0% | live |
| Vulnerability | CVE-2026-21955cve-2026-21955 | 0% | live |
| Vulnerability | CVE-2026-21956cve-2026-21956 | 0% | live |
| Vulnerability | CVE-2026-28221cve-2026-28221 | 0% | live |
| Vulnerability | CVE-2026-34045cve-2026-34045 | 0% | live |
| Vulnerability | CVE-2026-34445cve-2026-34445 | 0% | live |
| Vulnerability | CVE-2026-41309cve-2026-41309 | 0% | live |
| Vulnerability | CVE-2026-42579cve-2026-42579 | 0% | live |
| Vulnerability | Microsoft Defender Denial of Service Vulnerabilitycve-2026-45498 | 0% | live |
Showing top 30 of 35 by confidence. Click any target to see the full neighbourhood.
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.