CWE · MITRE source
CWE-406Insufficient 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.
Last updated: 22 August 2026 14:14 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls that address this weakness (4)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
CP-7 | Alternate Processing Site | CP | Limits attacker success in sustaining network amplification DoS against the primary by providing a ready alternate processing capability. |
CP-8 | Telecommunications Services | CP | Provides continuity when primary telecom is disrupted by insufficient control of network message volume or amplification. |
SC-47 | Alternate Communications Paths | SC | Network-volume amplification against one channel can be bypassed via the pre-established alternate path. |
SC-5 | Denial-of-service Protection | SC | Implements network message volume controls to block amplification DoS vectors. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-0028 KEV UPD | 8.8 | 8.6 | 0.0237 | 2022-08-10 |
CVE-2021-38487 UPD | 6.7 | 8.2 | 0.0325 | 2022-05-05 |
CVE-2021-38425 UPD | 6.5 | 7.5 | 0.0503 | 2022-05-05 |
CVE-2021-43547 UPD | 6.3 | 7.5 | 0.0243 | 2022-05-05 |
CVE-2021-38135 UPD | 6.2 | 8.6 | 0.0044 | 2024-11-22 |
CVE-2020-10772 UPD | 6.1 | 7.5 | 0.0135 | 2020-11-27 |
CVE-2026-54609 | 6.1 | 8.6 | 0.0026 | 2026-07-28 |
CVE-2021-4234 UPD | 6.0 | 7.5 | 0.0085 | 2022-07-06 |
CVE-2024-25015 UPD | 6.0 | 7.5 | 0.0092 | 2024-05-01 |
CVE-2023-28455 UPD | 5.9 | 7.5 | 0.0053 | 2024-09-18 |
CVE-2023-28456 UPD | 5.9 | 7.5 | 0.0054 | 2024-09-18 |
CVE-2023-49203 UPD | 5.9 | 7.5 | 0.0065 | 2024-09-18 |
CVE-2021-38429 UPD | 5.4 | 6.6 | 0.0141 | 2022-05-05 |
CVE-2026-68080 | 5.1 | 6.5 | 0.0042 | 2026-08-05 |
CVE-2026-45557 UPD | 4.5 | 5.8 | 0.0039 | 2026-05-19 |
CVE-2025-58066 UPD | 4.4 | 5.3 | 0.0034 | 2025-08-29 |
CVE-2026-50045 | 4.3 | 5.3 | 0.0028 | 2026-07-22 |
CVE-2019-14850 UPD | 3.6 | 3.7 | 0.0160 | 2021-03-18 |
CVE-2014-125036 UPD | 2.6 | 2.6 | 0.0040 | 2023-01-02 |