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.

Definição

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 no 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.

Como os atacantes a exploram

Trajeto do atacante passo a passo

  1. 1

    Identificar um caminho de código que trata input não confiável sem validação.

  2. 2

    Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.

  3. 3

    Entregar o payload através de um pedido normal e observar a reação da aplicação.

  4. 4

    Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.

Exemplo de código vulnerável

Vulnerable PHP

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

Vulnerável 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;
```
...*
Exemplo 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 verificação de prevenção

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.
Sinais de deteção

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.

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-698 e abre um PR de correção em menos de 60 segundos.

O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o 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.

Qual a gravidade do CWE-698?

A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.

Que linguagens ou plataformas são afetadas pelo CWE-698?

A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.

Como posso prevenir o 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.

Como é que o Plexicus deteta e corrige o CWE-698?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-698 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.

Onde posso saber mais sobre o CWE-698?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/698.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-698

CWE-705 Pai

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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

Pronto quando você estiver

Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.

O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.

Começar grátis Reservar uma demo