Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.
CWE-25 Variante Incompleto
Path Traversal: '/../filedir'
This vulnerability, often called directory traversal, occurs when an application builds a file path using user input without properly blocking sequences like '/../'. This lets an attacker break out…
Definición
What is CWE-25?
This vulnerability, often called directory traversal, occurs when an application builds a file path using user input without properly blocking sequences like '/../'. This lets an attacker break out of the intended directory and access files or folders elsewhere on the server.
At its core, this flaw allows an attacker to manipulate file paths by injecting '../' sequences. When the application doesn't filter these out, the server's filesystem interprets them to move up directories, potentially exposing sensitive configuration files, source code, or user data that should be inaccessible.
A common oversight is only checking for '../' at the very start of the input. Attackers can bypass this weak defense by using a leading slash, as in '/../payload'. This simple variation underscores why robust, context-aware validation is needed, not just simple string matching, to fully neutralize path traversal attempts.
Impacto en el mundo real
Real-world CVEs caused by CWE-25
-
A cloud management tool allows attackers to bypass the restricted shell using path traversal sequences like "/../" in the USER environment variable.
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 pseudo
MITRE no ha publicado un ejemplo de código para esta CWE. El patrón siguiente es ilustrativo — consulta Recursos para referencias canónicas.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} 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-25
- Implementation Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434. Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.
- Implementation Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Señales de detección
How to detect CWE-25
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.
Plexicus detecta automáticamente CWE-25 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.
Preguntas frecuentes ¿Qué es CWE-25?
¿Qué gravedad tiene CWE-25?
¿Qué lenguajes o plataformas se ven afectados por CWE-25?
¿Cómo puedo prevenir CWE-25?
¿Cómo detecta y corrige Plexicus CWE-25?
¿Dónde puedo aprender más sobre CWE-25?
Frequently asked questions
¿Qué es CWE-25?
This vulnerability, often called directory traversal, occurs when an application builds a file path using user input without properly blocking sequences like '/../'. This lets an attacker break out of the intended directory and access files or folders elsewhere on the server.
¿Qué gravedad tiene CWE-25?
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-25?
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-25?
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and…
¿Cómo detecta y corrige Plexicus CWE-25?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-25 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-25?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/25.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-25
CWE-23 Padre
Relative Path Traversal
This vulnerability occurs when an application builds file paths using user-supplied input without properly validating or sanitizing it.…
CWE-24 Hermano
Path Traversal: '../filedir'
Path traversal, often called directory traversal, occurs when an application builds a file path using user input without properly blocking…
CWE-26 Hermano
Path Traversal: '/dir/../filename'
This vulnerability occurs when an application builds a file path using user input but fails to properly block directory traversal…
CWE-27 Hermano
Path Traversal: 'dir/../../filename'
This vulnerability occurs when an application builds file paths using user input but fails to properly block sequences like…
CWE-28 Hermano
Path Traversal: '..\filedir'
This vulnerability occurs when an application builds a file path using user input but fails to block or properly handle '..\' sequences.…
CWE-29 Hermano
Path Traversal: '\..\filename'
This vulnerability occurs when an application builds file paths using user input but fails to block '\..\filename' sequences. Attackers…
CWE-30 Hermano
Path Traversal: '\dir\..\filename'
This vulnerability occurs when an application builds file paths using user input but fails to properly sanitize sequences like…
CWE-31 Hermano
Path Traversal: 'dir\..\..\filename'
This vulnerability occurs when an application builds file paths using user input but fails to properly block sequences like…
CWE-32 Hermano
Path Traversal: '...' (Triple Dot)
This vulnerability occurs when an application builds file paths using user input but fails to properly filter out '...' (triple dot)…
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.