CWE-406: Insufficient Control of Network Message Volume (Network Amplification)

ClassIncomplete

The product does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the product to transmit more traffic than should be allowed for that actor.

View on MITRE
Back to CWE Lookup

Extended Description

In the absence of a policy to restrict asymmetric resource consumption, the application or system cannot distinguish between legitimate transmissions and traffic intended to serve as an amplifying attack on target systems. Systems can often be configured to restrict the amount of traffic sent out on behalf of a client, based on the client's origin or access level. This is usually defined in a resource allocation policy. In the absence of a mechanism to keep track of transmissions, the system or application can be easily abused to transmit asymmetrically greater traffic than the request or client should be permitted to.

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-406 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-406, Insufficient Control of Network Message Volume (Network 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 Framework — National Institute of Standards and Technology

Apply Separation of Privilege controls for Insufficient Control of Network Message Volume (Network Amplification)

MITRE associates mitigation with Architecture and Design, Policy, and Implementation; the listed strategies include Separation of Privilege; documented detection approaches include Automated Static Analysis. Use these source-defined anchors to turn CWE-406 into implementation, review, and verification checks for the affected component.

CWE-406: Insufficient Control of Network Message Volume (Network Amplification) — MITRE CWE

Triage CWE-406 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-406, Insufficient Control of Network Message Volume (Network 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 Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-406

Apply MITRE's full root-cause mapping guidance when using CWE-406, Insufficient Control of Network Message Volume (Network 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 Guidance — MITRE CWE

Validate CWE-406 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-406, Insufficient Control of Network Message Volume (Network 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 Tips — MITRE CWE

Frequently Asked Questions

What is CWE-406: Insufficient Control of Network Message Volume (Network Amplification)?+

CWE-406: Insufficient Control of Network Message Volume (Network Amplification) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the product to transmit more traffic than should be allowed for that actor. In the absence of a policy to restrict asymmetric resource consumption, the application or system cannot distinguish between legitimate transmissions and traffic intended to serve as an amplifying attack on target systems. Systems can often be configured to restrict the amount of traffic sent out on behalf of a client, based on the client's origin or access level. This is usually defined in a resource allocation policy. In the absence of a mechanism to keep track of transmissions, the system or application can be easily abused to transmit asymmetrically greater traffic than the request or client should be permitted to.

What are the security consequences of Insufficient Control of Network Message Volume (Network Amplification)?+

If exploited, CWE-406 (Insufficient Control of Network Message Volume (Network Amplification)) it can compromise Availability, leading to outcomes such as DoS: Amplification, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory) and DoS: Resource Consumption (Other).

How do you prevent or mitigate Insufficient Control of Network Message Volume (Network Amplification)?+

Recommended mitigations for CWE-406 include: An application must make network resources available to a client commensurate with the client's access level. Define a clear policy for network resource allocation and consumption. An application must, at all times, keep track of network resources and meter their usage appropriately.

Which programming languages are affected by Insufficient Control of Network Message Volume (Network Amplification)?+

CWE-406 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 Insufficient Control of Network Message Volume (Network Amplification)?+

MITRE documents real CVEs mapped to CWE-406, including CVE-1999-0513, CVE-1999-1379, CVE-2000-0041, CVE-1999-1066 and CVE-2013-5211. 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-406 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

Find Related CVEs

Search for vulnerabilities that exploit CWE-406

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement