CWE-918 Base Incomplet

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

Définition

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.
Impact réel

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.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

  1. 1

    Identifier un chemin de code qui traite des entrées non fiables sans validation.

  2. 2

    Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.

  3. 3

    Délivrer la charge utile via une requête normale et observer la réaction de l'application.

  4. 4

    Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.

Exemple de code vulnérable

Vulnerable pseudo

MITRE n'a pas publié d'exemple de code pour ce CWE. Le motif ci-dessous est illustratif — voir Ressources pour les références canoniques.

Vulnérable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Exemple de code sécurisé

Secure pseudo

Sécurisé 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.
Liste de contrôle de prévention

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.
Signaux de détection

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

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-918 et ouvre une PR de correction en moins de 60 secondes.

Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.

Obtenir une démo Essayer Plexicus gratuitement
Questions fréquentes

Frequently asked questions

Qu'est-ce que 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.

Quelle est la gravité de CWE-918 ?

MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.

Quels langages ou plateformes sont affectés par CWE-918 ?

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

Comment puis-je prévenir 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.

Comment Plexicus détecte et corrige CWE-918 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-918 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-918 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/918.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-918

CWE-441 Parent

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 Frère

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…

Ressources

Further reading

Prêt quand vous l'êtes

Arrêtez de payer par développeur.
Commencez à fermer la boucle.

Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.

Commencer gratuitement Réserver une démo