CWE-766
Critical Data Element Declared Public
Incomplete
2009-05-27
00h00 +00:00
00h00 +00:00
2024-02-29
00h00 +00:00
00h00 +00:00
Notificações para um CWE
Fique informado sobre quaisquer alterações para um CWE específico.
Nome: Critical Data Element Declared Public
The product declares a critical variable, field, or member to be public when intended security policy requires it to be private.
Informações Gerais
Modos de Introdução
ImplementationPlataformas Aplicáveis
Linguagem
Name: C++ (Undetermined)Name: C# (Undetermined)
Name: Java (Undetermined)
Consequências Comuns
| Escopo | Impacto | Probabilidade |
|---|---|---|
| Integrity Confidentiality | Read Application Data, Modify Application Data Note: Making a critical variable public allows anyone with access to the object in which the variable is contained to alter or read the value. | |
| Other | Reduce Maintainability |
Exemplos Observados
| Referências | Descrição |
|---|---|
CVE-2010-3860 | variables declared public allow remote read of system properties such as user name and home directory. |
Mitigações Potenciais
Phases : ImplementationData should be private, static, and final whenever possible. This will assure that your code is protected by instantiating early, preventing access, and preventing tampering.
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 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.
Referências
REF-960
Automated Source Code Maintainability Measure (ASCMM)Object Management Group (OMG).
https://www.omg.org/spec/ASCMM/
Submissão
| Nome | Organização | Data | Data de lançamento | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 1.4 |
Modificações
| Nome | Organização | Data | Comentário |
|---|---|---|---|
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Common_Consequences, Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Likelihood_of_Exploit, Relationships | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Name, References, Relationships, Taxonomy_Mappings, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Detection_Factors, References, Relationships, Time_of_Introduction, Type | |
| CWE Content Team | MITRE | updated Mapping_Notes, Relationships | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Demonstrative_Examples |
