Nama: 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.

Informasi Umum

Mode Pengenalan

Implementation

Platform yang Berlaku

Bahasa

Nama: C++ (Undetermined)
Nama: C# (Undetermined)
Nama: Java (Undetermined)

Konsekuensi Umum

Cakupan	Dampak	Kemungkinan
Integrity Confidentiality	Read Application Data, Modify Application Data Catatan: 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 Catatan: This issue makes it more difficult to maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.

Contoh yang Diamati

Referensi	Deskripsi
CVE-2010-3860	variables declared public allow remote read of system properties such as user name and home directory.

Mitigasi yang Memungkinkan

Phases : Implementation
Data should be private, static, and final whenever possible. This will assure that your code is protected by instantiating early, preventing access, and preventing tampering.

Metode Deteksi

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.)
Efektivitas : High

Catatan Pemetaan Kerentanan

Justifikasi : 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.
Komentar : 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.

Referensi

REF-960

Automated Source Code Maintainability Measure (ASCMM)
Object Management Group (OMG).
https://www.omg.org/spec/ASCMM/

Pengajuan

Nama	Organisasi	Tanggal	Tanggal rilis	Version
CWE Content Team	MITRE	2009-03-03 +00:00	2009-05-27 +00:00	1.4

Modifikasi

Nama	Organisasi	Tanggal	Komentar
CWE Content Team	MITRE	2009-12-28 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2010-12-13 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences, Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2012-05-11 +00:00	updated Relationships
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2017-11-08 +00:00	updated Likelihood_of_Exploit, Relationships
CWE Content Team	MITRE	2019-01-03 +00:00	updated Common_Consequences, Description, Name, References, Relationships, Taxonomy_Mappings, Weakness_Ordinalities
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 Detection_Factors, References, Relationships, Time_of_Introduction, Type
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes, Relationships
CWE Content Team	MITRE	2023-10-26 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2024-02-29 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description

Detail CWE-766

CWE-766