CWE-406: Insufficient Control of Network Message Volume Skip to content

Security weakness

CWE-406 Insufficient Control of Network Message Volume

A class-level weakness that can lead to downtime and lost sales. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-406?

Insufficient Control of Network Message Volume (Network Amplification): 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.

Business impact

What CWE-406 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • DoS: Amplification
  • DoS: Crash, Exit, or Restart
  • DoS: Resource Consumption (CPU)

Free security check

Is CWE-406 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-406

Insufficient Control of Network Message Volume (Network Amplification)

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.

Weakness ID
CWE-406
Type
Class
Status
Incomplete
Introduced during
Operation, Architecture and Design, Implementation

Prevention

How to fix CWE-406, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • An application must make network resources available to a client commensurate with the client’s access level.
  2. 02

    Implementation

    • An application must, at all times, keep track of network resources and meter their usage appropriately.
  3. 03

    Policy

    • Define a clear policy for network resource allocation and consumption.

Detection and evidence

How CWE-406 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.

Real vulnerabilities it caused

  • CVE-1999-0513Classic "Smurf" attack, using spoofed ICMP packets to broadcast addresses.
  • CVE-1999-1379DNS query with spoofed source address causes more traffic to be returned to spoofed address than was sent by the attacker.
  • CVE-2000-0041Large datagrams are sent in response to malformed datagrams.
  • CVE-1999-1066Game server sends a large amount.
  • CVE-2013-5211composite: NTP feature generates large responses (high amplification factor) with spoofed UDP source addresses.

How we fix it

From finding to fixed: how Codefreex closes CWE-406

  1. 01

    Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. 02

    Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. 03

    Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. 04

    Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

Related weaknesses

FAQ

CWE-406: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-406?

CWE-406, “Insufficient Control of Network Message Volume (Network Amplification)”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. 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.

How serious is CWE-406?

It can affect availability, with impacts such as dos: amplification, dos: crash, exit, or restart, dos: resource consumption (cpu). The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-406?

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.

Can Codefreex check my site for CWE-406?

Yes. A senior engineer reviews your site, store or app for CWE-406 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-406 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.