1607
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name
Software Fault Patterns SFP21 Multiple locks/unlocks
CWE-766: Critical Data Element Declared Public
Weakness ID : 766
Structure : Simple
Abstraction : Base
Description
The product declares a critical variable, field, or member to be public when intended security policy
requires it to be private.
Extended Description
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. It also might make it
easier to introduce vulnerabilities.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 1061 Insufficient Encapsulation 1898
ChildOf 732 Incorrect Permission Assignment for Critical Resource 1551
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 275 Permission Issues 2317
Weakness Ordinalities
Primary :
Indirect :
Applicable Platforms
Language : C++ (Prevalence = Undetermined)
Language : C# (Prevalence = Undetermined)
Language : Java (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Integrity
Confidentiality
Read Application Data
Modify Application Data
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
CWE Version 4.14
CWE-766: Critical Data Element Declared Public
CWE-766: Critical Data Element Declared Public