CWE-698 Base Incompleto

Execution After Redirect (EAR)

Execution After Redirect (EAR) occurs when a web application sends a redirect response to a user's browser but continues to run server-side code, potentially performing unintended actions.

Definición

What is CWE-698?

Execution After Redirect (EAR) occurs when a web application sends a redirect response to a user's browser but continues to run server-side code, potentially performing unintended actions.
This vulnerability happens because the server-side logic doesn't properly halt execution after issuing a redirect command (like an HTTP 302 or 303 status). Instead of stopping, the application proceeds to execute the remaining code in the script or function. This leftover code can perform dangerous operations like updating databases, processing payments, or changing user sessions, even though the user is already being sent to a new page. From a security perspective, EAR is dangerous because an attacker can often interrupt or ignore the redirect. By using tools or crafting requests, they can let the redirect happen in the browser while still receiving and acting upon the results of the unauthorized server-side execution. To prevent this, developers must ensure the application flow terminates immediately after sending a redirect, typically by using explicit return or exit statements in the code.
Impacto en el mundo real

Real-world CVEs caused by CWE-698

  • CVE-2013-1402

    Execution-after-redirect allows access to application configuration details.

  • CVE-2009-1936

    chain: library file sends a redirect if it is directly requested but continues to execute, allowing remote file inclusion and path traversal.

  • CVE-2007-2713

    Remote attackers can obtain access to administrator functionality through EAR.

  • CVE-2007-4932

    Remote attackers can obtain access to administrator functionality through EAR.

  • CVE-2007-5578

    Bypass of authentication step through EAR.

  • CVE-2007-2713

    Chain: Execution after redirect triggers eval injection.

  • CVE-2007-6652

    chain: execution after redirect allows non-administrator to perform static code injection.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    Identifica una ruta de código que maneje entrada no confiable sin validación.

  2. 2

    Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.

  3. 3

    Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.

  4. 4

    Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.

Ejemplo de código vulnerable

Vulnerable PHP

This code queries a server and displays its status when a request comes from an authorized IP address.

Vulnerable PHP 
$requestingIP = $_SERVER['REMOTE_ADDR'];
  if(!in_array($requestingIP,$ipAllowList)){
  	echo "You are not authorized to view this page";
  	http_redirect($errorPageURL);
  }
  $status = getServerStatus();
  echo $status;
```
...*
Ejemplo de código seguro

Secure pseudo

Seguro 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-698

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Señales de detección

How to detect CWE-698

Black Box

This issue might not be detected if testing is performed using a web browser, because the browser might obey the redirect and move the user to a different page before the application has produced outputs that indicate something is amiss.

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-698 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-698?

Execution After Redirect (EAR) occurs when a web application sends a redirect response to a user's browser but continues to run server-side code, potentially performing unintended actions.

¿Qué gravedad tiene CWE-698?

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-698?

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-698?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

¿Cómo detecta y corrige Plexicus CWE-698?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-698 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-698?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/698.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-698

CWE-705 Padre

Incorrect Control Flow Scoping

This vulnerability occurs when a program fails to return execution to the correct point in the code after finishing a specific operation…

CWE-248 Hermano

Uncaught Exception

This vulnerability occurs when a function throws an error or exception, but the calling code does not have a proper handler to catch and…

CWE-382 Hermano

J2EE Bad Practices: Use of System.exit()

This vulnerability occurs when a J2EE application directly calls System.exit(), which forcibly terminates the entire application server…

CWE-395 Hermano

Use of NullPointerException Catch to Detect NULL Pointer Dereference

Using a try-catch block for NullPointerException as a substitute for proper null checks is an anti-pattern. This approach masks the root…

CWE-396 Hermano

Declaration of Catch for Generic Exception

This weakness occurs when code catches a generic exception type like 'Exception' or 'Throwable', which can hide specific errors and create…

CWE-397 Hermano

Declaration of Throws for Generic Exception

This vulnerability occurs when a method is declared to throw an overly broad exception type, such as a generic 'Exception' or 'Throwable'.…

CWE-455 Hermano

Non-exit on Failed Initialization

This vulnerability occurs when software continues to run as normal after encountering a critical security failure during its startup…

CWE-584 Hermano

Return Inside Finally Block

This vulnerability occurs when a function places a return statement inside a finally block. This dangerous pattern silently discards any…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo