CWE-405: Asymmetric Resource Consumption (Amplification)

ClassIncomplete

The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."

View on MITRE
Back to CWE Lookup

Extended Description

This can lead to poor performance due to "amplification" of resource consumption, typically in a non-linear fashion. This situation is worsened if the product allows malicious users or attackers to consume more resources than their access level permits.

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms
Not OS-Specific

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-405 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-405, Asymmetric Resource Consumption (Amplification), throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Address Asymmetric Resource Consumption (Amplification) during Architecture and Design

MITRE associates mitigation with Architecture and Design, and System Configuration; recorded impacts include DoS: Amplification, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), and DoS: Resource Consumption (Other); observed examples include CVE-1999-0513, CVE-2003-1564, and CVE-2004-2458. Use these source-defined anchors to turn CWE-405 into implementation, review, and verification checks for the affected component.

CWE-405: Asymmetric Resource Consumption (Amplification)MITRE CWE

Triage CWE-405 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-405, Asymmetric Resource Consumption (Amplification), has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-405

Apply MITRE's full root-cause mapping guidance when using CWE-405, Asymmetric Resource Consumption (Amplification). Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-405 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-405, Asymmetric Resource Consumption (Amplification). Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-405: Asymmetric Resource Consumption (Amplification)?+

CWE-405: Asymmetric Resource Consumption (Amplification) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric." This can lead to poor performance due to "amplification" of resource consumption, typically in a non-linear fashion. This situation is worsened if the product allows malicious users or attackers to consume more resources than their access level permits.

What are the security consequences of Asymmetric Resource Consumption (Amplification)?+

If exploited, CWE-405 (Asymmetric Resource Consumption (Amplification)) it can compromise Availability, leading to outcomes such as DoS: Amplification, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory) and DoS: Resource Consumption (Other).

How do you prevent or mitigate Asymmetric Resource Consumption (Amplification)?+

Recommended mitigations for CWE-405 include: An application must make resources available to a client commensurate with the client's access level. An application must, at all times, keep track of allocated resources and meter their usage appropriately. Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.

Which programming languages are affected by Asymmetric Resource Consumption (Amplification)?+

CWE-405 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Asymmetric Resource Consumption (Amplification)?+

MITRE documents real CVEs mapped to CWE-405, including CVE-1999-0513, CVE-2003-1564, CVE-2004-2458, CVE-2020-10735 and CVE-2020-5243. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-405 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement