Exécuter une analyse statique (SAST) sur le code source à la recherche du motif non sécurisé dans le flux de données.
CWE-288 Base Incomplet
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.
Définition
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.
Impact réel
Real-world CVEs caused by CWE-288
-
Router allows remote attackers to read system logs without authentication by directly connecting to the login screen and typing certain control characters.
-
Attackers with physical access to the machine may bypass the password prompt by pressing the ESC (Escape) key.
-
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.
-
Direct request of installation file allows attacker to create administrator accounts.
-
Attackers may gain additional privileges by directly requesting the web management URL.
-
Bypass authentication via direct request to named pipe.
-
User can avoid lockouts by using an API instead of the GUI to conduct brute force password guessing.
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 1
Identifier un chemin de code qui traite des entrées non fiables sans validation.
- 2
Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.
- 3
Délivrer la charge utile via une requête normale et observer la réaction de l'application.
- 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 Verilog
assign addr_auth = (address == 32'hF00) ? 1: 0; Exemple de code sécurisé
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.
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.
Liste de contrôle de prévention
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.
Signaux de détection
How to detect CWE-288
Exécuter des tests de sécurité applicative dynamique (DAST) contre le point de terminaison en ligne.
Surveiller les journaux runtime pour détecter des traces d'exception inhabituelles, des entrées malformées ou des tentatives de contournement d'autorisation.
Revue de code : signaler tout nouveau code qui traite les entrées de cette surface sans utiliser les helpers du framework validés.
CWE-288
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Questions fréquentes Qu'est-ce que CWE-288 ?
Quelle est la gravité de CWE-288 ?
Quels langages ou plateformes sont affectés par CWE-288 ?
Comment puis-je prévenir CWE-288 ?
Comment Plexicus détecte et corrige CWE-288 ?
Où puis-je en savoir plus sur CWE-288 ?
Frequently asked questions
Qu'est-ce que 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.
Quelle est la gravité de CWE-288 ?
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-288 ?
MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.
Comment puis-je prévenir 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.
Comment Plexicus détecte et corrige CWE-288 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-288 à 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-288 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/288.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-288
CWE-306 Parent
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 Frère
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 Pair
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 Enfant
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 Enfant
Direct Request ('Forced Browsing')
This vulnerability occurs when a web application fails to verify user permissions for every protected page, file, or API endpoint,…
Prêt à valider l'essentiel ?
Prêt à valider ce qui compte.
Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.