CWE-243
Creation of chroot Jail Without Changing Working Directory
2006-07-19
00h00 +00:00
00h00 +00:00
Notificações para um CWE
Fique informado sobre quaisquer alterações para um CWE específico.
Nome: Creation of chroot Jail Without Changing Working Directory
The product uses the chroot() system call to create a jail, but it does not change the working directory afterward.
Informações Gerais
Detalhes de Contexto
Modos de Introdução
Implementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.Plataformas Aplicáveis
Linguagem
Nome: C (Undetermined)Nome: C++ (Undetermined)
Sistemas Operacionais
Classe: Unix (Undetermined)Consequências Comuns
| Escopo | Impacto | Probabilidade |
|---|---|---|
| Confidentiality Integrity | Read Files or Directories, Modify Files or Directories Nota: If the working directory is not changed after the chroot() call, relative paths may still refer to file system resources outside of the jail. Attackers may be able to read or write to files outside of the jail. |
Métodos de Detecção
Automated Static Analysis
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.)Eficácia : High
Notas de Mapeamento de Vulnerabilidade
Justificativa : This CWE entry is at the Variant 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.
Referências
REF-6
Seven Pernicious Kingdoms: A Taxonomy of Software Security ErrorsKatrina Tsipenyuk, Brian Chess, Gary McGraw.
https://cwe.mitre.org/documents/sources/SevenPerniciousKingdoms.pdf
Submissão
| Nome | Organização | Data | Data de lançamento | Version |
|---|---|---|---|---|
| 7 Pernicious Kingdoms | Draft 3 |
Modificações
| Nome | Organização | Data | Comentário |
|---|---|---|---|
| CWE Content Team | MITRE | updated Applicable_Platforms, Background_Details, Description, Relationships, Taxonomy_Mappings, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Name | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Affected_Resources, Causal_Nature, Modes_of_Introduction, Relationships | |
| CWE Content Team | MITRE | updated References | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Detection_Factors, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Background_Details, Common_Consequences, Description, References |
