Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-282 Classe Rascunho
Improper Ownership Management
This vulnerability occurs when a system incorrectly assigns or fails to verify which user or process rightfully controls a specific object or resource.
Definição
What is CWE-282?
This vulnerability occurs when a system incorrectly assigns or fails to verify which user or process rightfully controls a specific object or resource.
At its core, this flaw is about broken trust in access control. It happens when software doesn't properly track or validate the true 'owner' of a file, memory block, database record, or system object. This can allow unauthorized users to delete, modify, or access resources they shouldn't, simply because the system believes they own them. Think of it as handing your house keys to a stranger because a faulty system incorrectly listed them as the homeowner.
For developers, the main risk is that operations which should be restricted to a resource's creator—like deletion or permission changes—become available to others. To prevent this, always explicitly validate ownership through a trusted authority (like a kernel or central service) before performing sensitive actions. Never rely on unverified user-supplied claims or transient identifiers that can be forged or reused. Implement clear, centralized ownership lifecycle management for all critical resources.
Impacto no mundo real
Real-world CVEs caused by CWE-282
-
Program runs setuid root but relies on a configuration file owned by a non-root user.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
This function is part of a privileged program that takes input from users with potentially lower privileges.
- 2
This code does not confirm that the process to be killed is owned by the requesting user, thus allowing an attacker to kill arbitrary processes.
- 3
This function remedies the problem by checking the owner of the process before killing it:
Exemplo de código vulnerável
Vulnerable Python
This function is part of a privileged program that takes input from users with potentially lower privileges.
def killProcess(processID):
os.kill(processID, signal.SIGKILL) Exemplo de código seguro
Secure Python
This function remedies the problem by checking the owner of the process before killing it:
def killProcess(processID):
user = getCurrentUser()
```
#Check process owner against requesting user*
if getProcessOwner(processID) == user:
```
os.kill(processID, signal.SIGKILL)
return
else:
print("You cannot kill a process you don't own")
return 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-282
- Architecture and Design / Operation Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Sinais de deteção
How to detect CWE-282
O Plexicus deteta automaticamente o CWE-282 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-282?
Qual a gravidade do CWE-282?
Que linguagens ou plataformas são afetadas pelo CWE-282?
Como posso prevenir o CWE-282?
Como é que o Plexicus deteta e corrige o CWE-282?
Onde posso saber mais sobre o CWE-282?
Frequently asked questions
O que é o CWE-282?
This vulnerability occurs when a system incorrectly assigns or fails to verify which user or process rightfully controls a specific object or resource.
Qual a gravidade do CWE-282?
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-282?
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-282?
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Como é que o Plexicus deteta e corrige o CWE-282?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-282 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-282?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/282.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-282
CWE-284 Pai
Improper Access Control
The software fails to properly limit who can access a resource, allowing unauthorized users or systems to interact with it.
CWE-1191 Irmão
On-Chip Debug and Test Interface With Improper Access Control
This vulnerability occurs when a hardware chip's debug or test interface (like JTAG) lacks proper access controls. Without correct…
CWE-1220 Irmão
Insufficient Granularity of Access Control
This vulnerability occurs when a system's access controls are too broad, allowing unauthorized users or processes to read or modify…
CWE-1224 Irmão
Improper Restriction of Write-Once Bit Fields
This vulnerability occurs when hardware write-once protection mechanisms, often called 'sticky bits,' are incorrectly implemented,…
CWE-1231 Irmão
Improper Prevention of Lock Bit Modification
This vulnerability occurs when hardware or firmware uses a lock bit to protect critical system registers or memory regions, but fails to…
CWE-1233 Irmão
Security-Sensitive Hardware Controls with Missing Lock Bit Protection
This vulnerability occurs when a hardware device uses a lock bit to protect critical configuration registers, but the lock fails to…
CWE-1252 Irmão
CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations
This vulnerability occurs when a CPU's hardware is not set up to enforce a strict separation between writing data to memory and executing…
CWE-1257 Irmão
Improper Access Control Applied to Mirrored or Aliased Memory Regions
This vulnerability occurs when a hardware design maps the same physical memory to multiple addresses (aliasing or mirroring) but fails to…
CWE-1259 Irmão
Improper Restriction of Security Token Assignment
This vulnerability occurs when a System-on-a-Chip (SoC) fails to properly secure its Security Token mechanism. These tokens control which…
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.