CWE-708 Detalhe

CWE-708

Incorrect Ownership Assignment
2008-09-09
00h00 +00:00
Incomplete
2026-10-28
00h00 +00:00
CWE Mitre.org
Notificações para um CWE
Fique informado sobre quaisquer alterações para um CWE específico.
Gerenciar notificações

Nome: Incorrect Ownership Assignment

The product assigns an owner to a resource, but the owner is outside of the intended control sphere.

Informações Gerais

Modos de Introdução

Architecture and Design
Implementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Operation

Plataformas Aplicáveis

Linguagem

Classe: Not Language-Specific (Undetermined)

Consequências Comuns

Escopo Impacto Probabilidade
Confidentiality
Integrity		Read Application Data, Modify Application Data

Nota: This may allow the resource to be manipulated by actors outside of the intended control sphere. An attacker could read and modify data for which they do not have permissions to access directly.

Exemplos Observados

Referências Descrição

CVE-2024-43199

product installs binaries with potentially insecure user/group ownership

CVE-2007-5101

File system sets wrong ownership and group when creating a new file.

CVE-2007-4238

OS installs program with bin owner/group, allowing modification.

CVE-2007-1716

Manager does not properly restore ownership of a reusable resource when a user logs out, allowing privilege escalation.

CVE-2005-3148

Backup software restores symbolic links with incorrect uid/gid.

CVE-2005-1064

Product changes the ownership of files that a symlink points to, instead of the symlink itself.

CVE-2011-1551

Component assigns ownership of sensitive directory tree to a user account, which can be leveraged to perform privileged operations.

Mitigações Potenciais

Phases : Policy
Periodically review the privileges and their owners.

Métodos de Detecção

Automated Analysis

Use automated tools to check for privilege settings.

Notas de Mapeamento de Vulnerabilidade

Justificativa : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comentário : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Notas


Submissão

Nome Organização Data Data de lançamento Version
CWE Content Team MITRE 2008-09-09 +00:00 2008-09-09 +00:00 1.0

Modificações

Nome Organização Data Comentário
Eric Dalci Cigital 2008-07-01 +00:00 updated Potential_Mitigations, Time_of_Introduction
CWE Content Team MITRE 2009-03-10 +00:00 updated Relationships
CWE Content Team MITRE 2009-05-27 +00:00 updated Description
CWE Content Team MITRE 2011-06-01 +00:00 updated Common_Consequences, Maintenance_Notes, Other_Notes
CWE Content Team MITRE 2012-05-11 +00:00 updated Common_Consequences, Relationships
CWE Content Team MITRE 2012-10-30 +00:00 updated Observed_Examples, Potential_Mitigations
CWE Content Team MITRE 2014-07-30 +00:00 updated Relationships
CWE Content Team MITRE 2017-11-08 +00:00 updated Applicable_Platforms, Modes_of_Introduction, Relationships
CWE Content Team MITRE 2020-02-24 +00:00 updated Relationships
CWE Content Team MITRE 2023-01-31 +00:00 updated Description
CWE Content Team MITRE 2023-04-27 +00:00 updated Relationships
CWE Content Team MITRE 2023-06-29 +00:00 updated Mapping_Notes
CWE Content Team MITRE 2025-12-11 +00:00 updated Detection_Factors, Observed_Examples, Potential_Mitigations, Weakness_Ordinalities
CWE Content Team MITRE 2026-10-28 +00:00 updated Common_Consequences, Description
As informações apresentadas no CVE Find originam-se de várias fontes de referência cuidadosamente selecionadas. Os dados CVE são fornecidos pela MITRE Corporation e pelo National Vulnerability Database (NVD). O catálogo de Vulnerabilidades Conhecidas Exploradas (KEV) é proveniente da Cybersecurity and Infrastructure Security Agency (CISA), enquanto as pontuações EPSS vêm do FIRST.org. Além disso, os dados sobre fraquezas de software (CWE) e padrões de ataque comuns (CAPEC) são mantidos pela MITRE Corporation, e as informações sobre configurações de hardware e software (CPE) são fornecidas pelo NVD.