CWE-288 Base Incompleto

Authentication Bypass Using an Alternate Path or Channel

This vulnerability occurs when a system has a primary login requirement, but attackers can find an unprotected backdoor or alternative route that completely bypasses those checks.

Definición

What is CWE-288?

This vulnerability occurs when a system has a primary login requirement, but attackers can find an unprotected backdoor or alternative route that completely bypasses those checks.
Think of it like a building with a guarded front door but an unlocked side window. The main application flow correctly validates user credentials, but developers might overlook a secondary API endpoint, a hidden administrative page, a debug interface, or a direct file path that doesn't enforce the same authentication rules. Attackers discover these alternate channels through reconnaissance, fuzzing, or analyzing application structure, allowing them to access restricted functions or data without ever logging in. This often happens during development when temporary access points are created for testing and never removed, or when different system components have inconsistent security policies. To prevent it, you must ensure every single entry point into protected functionality—including APIs, files, and hidden directories—enforces the same robust authentication checks. Regular security audits should map all access paths and verify none provide a secret bypass to your core security gate.
Vulnerability Diagram CWE-288
Auth Bypass via Alternate Path /login password required /internal/api no auth (legacy) Same backend no second check Sensitive data accessible Hardened front door, side door wide open.
Impacto en el mundo real

Real-world CVEs caused by CWE-288

  • CVE-2000-1179

    Router allows remote attackers to read system logs without authentication by directly connecting to the login screen and typing certain control characters.

  • CVE-1999-1454

    Attackers with physical access to the machine may bypass the password prompt by pressing the ESC (Escape) key.

  • CVE-1999-1077

    OS allows local attackers to bypass the password protection of idled sessions via the programmer's switch or CMD-PWR keyboard sequence, which brings up a debugger that the attacker can use to disable the lock.

  • CVE-2003-0304

    Direct request of installation file allows attacker to create administrator accounts.

  • CVE-2002-0870

    Attackers may gain additional privileges by directly requesting the web management URL.

  • CVE-2002-0066

    Bypass authentication via direct request to named pipe.

  • CVE-2003-1035

    User can avoid lockouts by using an API instead of the GUI to conduct brute force password guessing.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    Identifica una ruta de código que maneje entrada no confiable sin validación.

  2. 2

    Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.

  3. 3

    Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.

  4. 4

    Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.

Ejemplo de código vulnerable

Vulnerable Verilog

Vulnerable Verilog 
assign addr_auth = (address == 32'hF00) ? 1: 0;
Ejemplo de código seguro

Secure Verilog

The bugged line of code is repeated in the Bad example above. Weakness arises from the fact that the SECURE_ME register can be modified by writing to the shadow register COPY_OF_SECURE_ME, the address of COPY_OF_SECURE_ME should also be included in the check. That buggy line of code should instead be replaced as shown in the Good Code Snippet below.

Seguro Verilog 
assign addr_auth = (address == 32'hF00 || address == 32'h800F00) ? 1: 0;
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-288

  • Architecture and Design Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.
Señales de detección

How to detect CWE-288

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

This vulnerability occurs when a system has a primary login requirement, but attackers can find an unprotected backdoor or alternative route that completely bypasses those checks.

¿Qué gravedad tiene CWE-288?

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

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

Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.

¿Cómo detecta y corrige Plexicus CWE-288?

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

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

Debilidades relacionadas

Weaknesses related to CWE-288

CWE-306 Padre

Missing Authentication for Critical Function

This vulnerability occurs when a software feature that performs a sensitive action or uses significant system resources does not verify…

CWE-322 Hermano

Key Exchange without Entity Authentication

This vulnerability occurs when a system establishes a cryptographic key with another party without first confirming that party's true…

CWE-420 Par

Unprotected Alternate Channel

This vulnerability occurs when an application secures its main communication path but leaves a backup or alternative channel with weaker…

CWE-1299 Hijo

Missing Protection Mechanism for Alternate Hardware Interface

This vulnerability occurs when a hardware component's security controls only protect the primary access path, leaving alternate interfaces…

CWE-425 Hijo

Direct Request ('Forced Browsing')

This vulnerability occurs when a web application fails to verify user permissions for every protected page, file, or API endpoint,…

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