Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.
CWE-267 Base Incompleto
Privilege Defined With Unsafe Actions
This vulnerability occurs when a system grants a user, role, or process a specific permission that can be misused to perform dangerous, unintended actions. The permission itself is correctly…
Definição
What is CWE-267?
This vulnerability occurs when a system grants a user, role, or process a specific permission that can be misused to perform dangerous, unintended actions. The permission itself is correctly assigned, but its scope is too broad or allows for unsafe operations.
At its core, this weakness is about over-privilege. A system might correctly identify that a user needs to edit files, but if the associated 'edit' permission also allows them to overwrite critical system files or execute code, the privilege is dangerously defined. Developers often make this mistake by using coarse-grained permissions that bundle safe and unsafe actions together, or by not considering all the destructive ways a seemingly benign right could be exploited.
To prevent this, implement the principle of least privilege by defining permissions based on specific, safe actions rather than broad capabilities. Audit your authorization logic to ensure each granted right cannot be chained or used in an unexpected context to cause harm. Security testing should explicitly check if assigned privileges can be leveraged to bypass security controls or perform actions outside the user's intended role.
Impacto no mundo real
Real-world CVEs caused by CWE-267
-
Roles have access to dangerous procedures (Accessible entities).
-
Untrusted object/method gets access to clipboard (Accessible entities).
-
Gain privileges using functions/tags that should be restricted (Accessible entities).
-
Traceroute program allows unprivileged users to modify source address of packet (Accessible entities).
-
Bypass domain restrictions using a particular file that references unsafe URI schemes (Accessible entities).
-
Script does not restrict access to an update command, leading to resultant disk consumption and filled error logs (Accessible entities).
-
"public" database user can use stored procedure to modify data controlled by the database owner (Unsafe privileged actions).
-
User with capability can prevent setuid program from dropping privileges (Unsafe privileged actions).
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 Java
This code intends to allow only Administrators to print debug information about a system.
public enum Roles {
ADMIN,USER,GUEST
}
public void printDebugInfo(User requestingUser){
if(isAuthenticated(requestingUser)){
switch(requestingUser.role){
case GUEST:
System.out.println("You are not authorized to perform this command");
break;
default:
System.out.println(currentDebugState());
break;
}
}
else{
System.out.println("You must be logged in to perform this command");
}
} 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-267
- Architecture and Design / Operation Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design / Operation Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
Sinais de deteção
How to detect CWE-267
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.
O Plexicus deteta automaticamente o CWE-267 e abre um PR de correção em menos de 60 segundos.
O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.
Perguntas frequentes O que é o CWE-267?
Qual a gravidade do CWE-267?
Que linguagens ou plataformas são afetadas pelo CWE-267?
Como posso prevenir o CWE-267?
Como é que o Plexicus deteta e corrige o CWE-267?
Onde posso saber mais sobre o CWE-267?
Frequently asked questions
O que é o CWE-267?
This vulnerability occurs when a system grants a user, role, or process a specific permission that can be misused to perform dangerous, unintended actions. The permission itself is correctly assigned, but its scope is too broad or allows for unsafe operations.
Qual a gravidade do CWE-267?
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-267?
A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.
Como posso prevenir o CWE-267?
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software. Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need…
Como é que o Plexicus deteta e corrige o CWE-267?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-267 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-267?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/267.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-267
CWE-269 Pai
Improper Privilege Management
This vulnerability occurs when an application fails to correctly manage user permissions, allowing someone to perform actions or access…
CWE-250 Irmão
Execution with Unnecessary Privileges
This vulnerability occurs when software runs with higher permissions than it actually needs to perform its tasks. This excessive privilege…
CWE-266 Irmão
Incorrect Privilege Assignment
This vulnerability occurs when a system mistakenly grants a user, process, or entity a specific permission or privilege they should not…
CWE-268 Irmão
Privilege Chaining
Privilege chaining occurs when an attacker combines two separate permissions or capabilities, neither of which is dangerous on its own, to…
CWE-270 Irmão
Privilege Context Switching Error
This vulnerability occurs when an application fails to properly manage user permissions while moving between different security contexts,…
CWE-271 Irmão
Privilege Dropping / Lowering Errors
This vulnerability occurs when a system or process fails to reduce its elevated permissions before transferring control of a resource to a…
CWE-274 Irmão
Improper Handling of Insufficient Privileges
This vulnerability occurs when an application fails to properly manage situations where it lacks the necessary permissions to execute an…
CWE-648 Irmão
Incorrect Use of Privileged APIs
This vulnerability occurs when software incorrectly uses functions that require special permissions. Attackers can exploit these mistakes…
CWE-623 Filho
Unsafe ActiveX Control Marked Safe For Scripting
This vulnerability occurs when an ActiveX control designed for limited use is incorrectly flagged as safe for scripting, allowing web…
Pronto quando você estiver
Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.
O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.