Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.
CWE-406 Clase Incompleto
Insufficient Control of Network Message Volume (Network Amplification)
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…
Definición
What is CWE-406?
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.
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.
Impacto en el mundo real
Real-world CVEs caused by CWE-406
-
Classic "Smurf" attack, using spoofed ICMP packets to broadcast addresses.
-
DNS query with spoofed source address causes more traffic to be returned to spoofed address than was sent by the attacker.
-
Large datagrams are sent in response to malformed datagrams.
-
Game server sends a large amount.
-
composite: NTP feature generates large responses (high amplification factor) with spoofed UDP source addresses.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
Identifica una ruta de código que maneje entrada no confiable sin validación.
- 2
Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.
- 3
Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.
- 4
Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.
Ejemplo de código vulnerable
Vulnerable Python
This code listens on a port for DNS requests and sends the result to the requesting address.
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock.bind( (UDP_IP,UDP_PORT) )
while true:
data = sock.recvfrom(1024)
if not data:
break
(requestIP, nameToResolve) = parseUDPpacket(data)
record = resolveName(nameToResolve)
sendResponse(requestIP,record) Ejemplo de código seguro
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención
How to prevent CWE-406
- Architecture and Design An application must make network resources available to a client commensurate with the client's access level.
- Policy Define a clear policy for network resource allocation and consumption.
- Implementation An application must, at all times, keep track of network resources and meter their usage appropriately.
Señales de detección
How to detect CWE-406
Ejecuta pruebas dinámicas de seguridad de aplicaciones (DAST) contra el endpoint en vivo.
Vigila los logs en tiempo de ejecución para detectar trazas de excepción inusuales, entradas malformadas o intentos de bypass de autorización.
Revisión de código: marca cualquier código nuevo que maneje entrada desde esta superficie sin usar los helpers validados del framework.
CWE-406
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Preguntas frecuentes ¿Qué es CWE-406?
¿Qué gravedad tiene CWE-406?
¿Qué lenguajes o plataformas se ven afectados por CWE-406?
¿Cómo puedo prevenir CWE-406?
¿Cómo detecta y corrige Plexicus CWE-406?
¿Dónde puedo aprender más sobre CWE-406?
Frequently asked questions
¿Qué es CWE-406?
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.
¿Qué gravedad tiene CWE-406?
MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.
¿Qué lenguajes o plataformas se ven afectados por CWE-406?
MITRE no ha especificado plataformas afectadas para esta CWE — puede aplicar a la mayoría de los stacks de aplicaciones.
¿Cómo puedo prevenir 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.
¿Cómo detecta y corrige Plexicus CWE-406?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-406 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-406?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/406.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-406
CWE-405 Padre
Asymmetric Resource Consumption (Amplification)
This vulnerability occurs when a system allows an attacker to trigger a disproportionate amount of resource consumption—like CPU, memory,…
CWE-1050 Hermano
Excessive Platform Resource Consumption within a Loop
This vulnerability occurs when a loop contains code that repeatedly consumes critical system resources like file handles, database…
CWE-1072 Hermano
Data Resource Access without Use of Connection Pooling
This weakness occurs when an application creates a new database connection for every request instead of using a managed connection pool.…
CWE-1073 Hermano
Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses
This weakness occurs when a client-side function or method makes an excessive number of individual data requests through a non-SQL data…
CWE-1084 Hermano
Invokable Control Element with Excessive File or Data Access Operations
This weakness occurs when a single function or method performs an excessive number of file or database operations, such as repeated reads,…
CWE-1089 Hermano
Large Data Table with Excessive Number of Indices
This weakness occurs when an application uses a database table with a very large number of rows and creates too many indexes on it,…
CWE-1094 Hermano
Excessive Index Range Scan for a Data Resource
This weakness occurs when a database query performs an index range scan that can access an unnecessarily large number of rows from a…
CWE-1176 Hermano
Inefficient CPU Computation
This weakness occurs when software uses inefficient algorithms or suboptimal CPU operations, performing unnecessary or overly complex…
CWE-407 Hermano
Inefficient Algorithmic Complexity
This vulnerability occurs when a software component uses an algorithm with poor worst-case performance. An attacker can exploit this by…
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.