CWE-918 Base Incompleto

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) occurs when a web application fetches a remote resource based on user-controlled input, but fails to properly validate or restrict where those requests are sent.…

Definição

What is CWE-918?

Server-Side Request Forgery (SSRF) occurs when a web application fetches a remote resource based on user-controlled input, but fails to properly validate or restrict where those requests are sent. This allows an attacker to trick the server into making unauthorized connections to internal systems or external domains.
SSRF flaws are dangerous because they let attackers bypass firewalls and access sensitive internal infrastructure that should be unreachable from the outside. A common scenario involves an application that takes a URL parameter for fetching an image or importing data, but an attacker manipulates it to target internal admin panels, cloud metadata services, or other backend systems. This can lead to information disclosure, internal service enumeration, or even remote code execution if the server processes the malicious response. Preventing SSRF requires a defense-in-depth approach: implement allowlists for permitted domains and protocols, validate and sanitize all user input used in network requests, and avoid using raw URLs to fetch resources. Network-level controls like segregating internal services and enforcing outbound firewall rules are also critical. While SAST and DAST tools can detect the vulnerable pattern, Plexicus uses AI to analyze the specific context and suggest the precise code fix—such as implementing a secure URL validator—saving significant manual remediation time across your application portfolio.
Vulnerability Diagram CWE-918
Server-Side Request Forgery (SSRF) Attacker url=http://169.254.… Web app fetch(url) no host allowlist runs in VPC Cloud metadata 169.254.169.254/iam Internal services redis:6379, admin:8080 Server fetches attacker URL → reaches resources only the server can.
Impacto no mundo real

Real-world CVEs caused by CWE-918

  • CVE-2024-3095

    SSRF in LLM application development framework because the URL retriever allows connections to local addresses using a crafted Location header

  • CVE-2023-32786

    Chain: LLM integration framework has prompt injection (CWE-1427) that allows an attacker to force the service to retrieve data from an arbitrary URL, essentially providing SSRF (CWE-918) and potentially injecting content into downstream tasks.

  • CVE-2021-26855

    Server Side Request Forgery (SSRF) in mail server, as exploited in the wild per CISA KEV.

  • CVE-2021-21973

    Server Side Request Forgery in cloud platform, as exploited in the wild per CISA KEV.

  • CVE-2016-4029

    Chain: incorrect validation of intended decimal-based IP address format (CWE-1286) enables parsing of octal or hexadecimal formats (CWE-1389), allowing bypass of an SSRF protection mechanism (CWE-918).

  • CVE-2002-1484

    Web server allows attackers to request a URL from another server, including other ports, which allows proxied scanning.

  • CVE-2004-2061

    CGI script accepts and retrieves incoming URLs.

  • CVE-2010-1637

    Web-based mail program allows internal network scanning using a modified POP3 port number.

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 pseudo

A MITRE não publicou um exemplo de código para este CWE. O padrão abaixo é ilustrativo — consulte os Recursos para referências canónicas.

Vulnerável pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
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-918

  • 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-918

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-918 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-918?

Server-Side Request Forgery (SSRF) occurs when a web application fetches a remote resource based on user-controlled input, but fails to properly validate or restrict where those requests are sent. This allows an attacker to trick the server into making unauthorized connections to internal systems or external domains.

Qual a gravidade do CWE-918?

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

MITRE lists the following affected platforms: AI/ML, Web Server.

Como posso prevenir o CWE-918?

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

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-918 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-918?

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

Fraquezas relacionadas

Weaknesses related to CWE-918

CWE-441 Pai

Unintended Proxy or Intermediary ('Confused Deputy')

A confused deputy vulnerability occurs when a system receives a request from a client and forwards it to an external destination without…

CWE-1021 Irmão

Improper Restriction of Rendered UI Layers or Frames

This vulnerability occurs when a web application fails to properly control whether its pages can be embedded within frames or UI layers…

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