CWE-795 Base Incompleto

Only Filtering Special Elements at a Specified Location

This vulnerability occurs when a security filter only checks for dangerous input patterns at specific, predefined locations within the data. It fails to scan the entire input stream, allowing…

Definición

What is CWE-795?

This vulnerability occurs when a security filter only checks for dangerous input patterns at specific, predefined locations within the data. It fails to scan the entire input stream, allowing malicious elements that appear outside the expected location to pass through and potentially harm downstream components.
Imagine a filter designed to remove semicolons, but it only checks the very beginning of a user-supplied string. An attacker can simply place the semicolon later in the input—for example, in the middle or at the end—to bypass the filter entirely. This creates a false sense of security because the filter is active, but its limited scope leaves the application exposed to the very attacks it was meant to prevent. This often happens when validation logic uses functions that only look for special characters at absolute positions (like 'byte 10') or relative to markers (like 'the second argument'). Developers must ensure their input sanitization processes perform a comprehensive check across the entire data payload, not just a single, predictable spot. The core failure is a logic error in the filter's design, not the absence of a filter.
Impacto en el mundo real

Real-world CVEs caused by CWE-795

Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    The following code takes untrusted input and uses a regular expression to filter a "../" element located at the beginning of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.

  2. 2

    Since the regular expression is only looking for an instance of "../" at the beginning of the string, it only removes the first "../" element. So an input value such as:

  3. 3

    will have the first "../" stripped, resulting in:

  4. 4

    This value is then concatenated with the /home/user/ directory:

  5. 5

    which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-22).

Ejemplo de código vulnerable

Vulnerable Perl

The following code takes untrusted input and uses a regular expression to filter a "../" element located at the beginning of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.

Vulnerable Perl 
my $Username = GetUntrustedInput();
  $Username =~ s/^\.\.\///;
  my $filename = "/home/user/" . $Username;
  ReadAndSendFile($filename);
Payload del atacante

Since the regular expression is only looking for an instance of "../" at the beginning of the string, it only removes the first "../" element. So an input value such as:

Payload del atacante 
../../../etc/passwd
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-795

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

SAST High

Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.

DAST Moderate

Ejecuta pruebas dinámicas de seguridad de aplicaciones (DAST) contra el endpoint en vivo.

Runtime Moderate

Vigila los logs en tiempo de ejecución para detectar trazas de excepción inusuales, entradas malformadas o intentos de bypass de autorización.

Code review Moderate

Revisión de código: marca cualquier código nuevo que maneje entrada desde esta superficie sin usar los helpers validados del framework.

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-795 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-795?

This vulnerability occurs when a security filter only checks for dangerous input patterns at specific, predefined locations within the data. It fails to scan the entire input stream, allowing malicious elements that appear outside the expected location to pass through and potentially harm downstream components.

¿Qué gravedad tiene CWE-795?

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

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

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

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

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

Debilidades relacionadas

Weaknesses related to CWE-795

CWE-791 Padre

Incomplete Filtering of Special Elements

This vulnerability occurs when an application accepts data from a source but fails to properly clean or neutralize all special characters…

CWE-792 Hermano

Incomplete Filtering of One or More Instances of Special Elements

This vulnerability occurs when an application receives external data but fails to properly neutralize all instances of potentially…

CWE-796 Hijo

Only Filtering Special Elements Relative to a Marker

This vulnerability occurs when software filters dangerous inputs or characters, but only checks for them in specific, expected locations…

CWE-797 Hijo

Only Filtering Special Elements at an Absolute Position

This vulnerability occurs when software checks for dangerous characters or patterns only at a fixed, hardcoded location in input data.…

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