Insufficient Control of Network Message Volume (Network Amplification)

Incomplete Class
Structure: Simple
Description

This vulnerability occurs when a system fails to properly limit the amount of network traffic it can generate in response to a request, allowing an attacker to abuse it to send a disproportionately large volume of data.

Extended Description

Without clear limits on how much traffic a single user or request can trigger, a system cannot tell the difference between normal operations and an attack designed to amplify traffic. Attackers exploit this by sending small, seemingly innocent requests that force the system to generate massive, overwhelming responses. This turns the vulnerable application into an unwitting participant in a denial-of-service attack against other targets. To prevent this, systems need a defined resource policy that tracks and caps outgoing transmissions based on client identity, privilege, or request type. Implementing such controls—like rate limiting, traffic quotas, or monitoring for abnormal response sizes—ensures that no single entity can commandeer your network resources to launch an amplified attack.

Common Consequences 1
Scope: Availability

Impact: DoS: AmplificationDoS: Crash, Exit, or RestartDoS: Resource Consumption (CPU)DoS: Resource Consumption (Memory)DoS: Resource Consumption (Other)

System resources can be quickly consumed leading to poor application performance or system crash. This may affect network performance and could be used to attack other systems and applications relying on network performance.

Potential Mitigations 3
Phase: Architecture and Design

Strategy: Separation of Privilege

An application must make network resources available to a client commensurate with the client's access level.
Phase: Policy
Define a clear policy for network resource allocation and consumption.
Phase: Implementation
An application must, at all times, keep track of network resources and meter their usage appropriately.
Demonstrative Examples 1

ID : DX-113

This code listens on a port for DNS requests and sends the result to the requesting address.

Code Example:

Bad
Python
python
This code sends a DNS record to a requesting IP address. UDP allows the source IP address to be easily changed ('spoofed'), thus allowing an attacker to redirect responses to a target, which may be then be overwhelmed by the network traffic.
Observed Examples 5
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.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Operation
Architecture and Design
Implementation
Taxonomy Mapping
  • PLOVER
Notes
RelationshipThis can be resultant from weaknesses that simplify spoofing attacks.
TheoreticalNetwork amplification, when performed with spoofing, is normally a multi-channel attack from attacker (acting as user) to amplifier, and amplifier to victim.