Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.
CWE-425 Base Incompleto
Direct Request ('Forced Browsing')
This vulnerability occurs when a web application fails to verify user permissions for every protected page, file, or API endpoint, allowing attackers to access them directly.
Definição
What is CWE-425?
This vulnerability occurs when a web application fails to verify user permissions for every protected page, file, or API endpoint, allowing attackers to access them directly.
Direct Request vulnerabilities happen because developers often assume users will only navigate through the intended application flow, like clicking buttons in a set sequence. They place authorization checks only at those expected entry points, forgetting that a user can simply type or forge a request to any URL or endpoint the server knows.
This creates an insecure direct object reference (IDOR) risk, where attackers can 'force browse' by guessing or discovering hidden paths to administrative panels, configuration files, user data, or backend scripts. To prevent this, every single restricted resource must independently validate that the current session has explicit permission to access it, regardless of how the request was made.
Impacto no mundo real
Real-world CVEs caused by CWE-425
-
Access-control setting in web-based document collaboration tool is not properly implemented by the code, which prevents listing hidden directories but does not prevent direct requests to files in those directories.
-
Python-based HTTP library did not scope cookies to a particular domain such that "supercookies" could be sent to any domain on redirect.
-
Bypass authentication via direct request.
-
Infinite loop or infoleak triggered by direct requests.
-
Bypass auth/auth via direct request.
-
Direct request leads to infoleak by error.
-
Direct request leads to infoleak by error.
-
Direct request leads to infoleak by error.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable JSP
If forced browsing is possible, an attacker may be able to directly access a sensitive page by entering a URL similar to the following.
http://somesite.com/someapplication/admin.jsp Payload do atacante
If forced browsing is possible, an attacker may be able to directly access a sensitive page by entering a URL similar to the following.
http://somesite.com/someapplication/admin.jsp Exemplo 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 verificação de prevenção
How to prevent CWE-425
- Architecture and Design / Operation Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
- Architecture and Design Consider using MVC based frameworks such as Struts.
Sinais de deteção
How to detect CWE-425
Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.
Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.
Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.
CWE-425
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.
Perguntas frequentes O que é o CWE-425?
Qual a gravidade do CWE-425?
Que linguagens ou plataformas são afetadas pelo CWE-425?
Como posso prevenir o CWE-425?
Como é que o Plexicus deteta e corrige o CWE-425?
Onde posso saber mais sobre o CWE-425?
Frequently asked questions
O que é o CWE-425?
This vulnerability occurs when a web application fails to verify user permissions for every protected page, file, or API endpoint, allowing attackers to access them directly.
Qual a gravidade do CWE-425?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-425?
MITRE lists the following affected platforms: Web Based.
Como posso prevenir o CWE-425?
Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files. Consider using MVC based frameworks such as Struts.
Como é que o Plexicus deteta e corrige o CWE-425?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-425 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-425?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/425.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-425
CWE-862 Pai
Missing Authorization
This vulnerability occurs when an application fails to verify whether a user has permission to access specific data or execute certain…
CWE-1314 Irmão
Missing Write Protection for Parametric Data Values
This vulnerability occurs when a hardware device fails to protect the scaling parameters used to convert raw sensor readings. Untrusted…
CWE-638 Irmão
Not Using Complete Mediation
This vulnerability occurs when software fails to verify access permissions every single time a user or process tries to use a resource.…
CWE-939 Irmão
Improper Authorization in Handler for Custom URL Scheme
This vulnerability occurs when an app implements a custom URL scheme handler but fails to properly verify which other apps or sources are…
CWE-471 Pode preceder
Modification of Assumed-Immutable Data (MAID)
This vulnerability occurs when an application fails to protect data it assumes cannot be changed, allowing an attacker to alter it.
CWE-98 Pode preceder
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
This vulnerability occurs when a PHP application uses unvalidated or insufficiently restricted user input directly within file inclusion…
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.