- Home
-
CWE-1294: Insecure Security Identifier Mechanism
Weakness ID: 1294Vulnerability Mapping: ALLOWED This CWE ID could be used to map to real-world vulnerabilities in limited situations requiring careful review (with careful review of mapping notes)
Abstraction: Class Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.View customized information:For users who are interested in more notional aspects of a weakness. Example: educators, technical writers, and project/program managers. For users who are concerned with the practical application and details about the nature of a weakness and how to prevent it from happening. Example: tool developers, security researchers, pen-testers, incident response analysts. For users who are mapping an issue to CWE/CAPEC IDs, i.e., finding the most appropriate CWE for a specific issue (e.g., a CVE record). Example: tool developers, security researchers. For users who wish to see all available information for the CWE/CAPEC entry. For users who want to customize what details are displayed.
Description
Extended Description
Common Consequences
This table specifies different individual consequences
associated with the weakness. The Scope identifies the application security area that is
violated, while the Impact describes the negative technical impact that arises if an
adversary succeeds in exploiting this weakness. The Likelihood provides information about
how likely the specific consequence is expected to be seen relative to the other
consequences in the list. For example, there may be high likelihood that a weakness will be
exploited to achieve a certain impact, but a low likelihood that it will be exploited to
achieve a different impact.
Impact Details Modify Memory; Read Memory; DoS: Resource Consumption (Other); Execute Unauthorized Code or Commands; Gain Privileges or Assume Identity; Quality Degradation
Scope: Confidentiality, Integrity, Availability, Access Control Likelihood: High
Potential Mitigations
Relationships
This table shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOf 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 the user
may want to explore.
Relevant to the view "Research Concepts" (View-1000)
Nature Type ID Name ChildOf 
Pillar - a weakness that is the most abstract type of weakness and represents a theme for all class/base/variant weaknesses related to it. A Pillar is different from a Category as a Pillar is still technically a type of weakness that describes a mistake, while a Category represents a common characteristic used to group related things.
284 Improper Access Control ParentOf 
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1302 Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)
Relevant to the view "Hardware Design" (View-1194)
Nature Type ID Name MemberOf 
Category - a CWE entry that contains a set of other entries that share a common characteristic.
1198 Privilege Separation and Access Control Issues ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1259 Improper Restriction of Security Token Assignment ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1270 Generation of Incorrect Security Tokens ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1290 Incorrect Decoding of Security Identifiers ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1292 Incorrect Conversion of Security Identifiers
Modes
Of IntroductionThe different Modes of Introduction provide information
about how and when this
weakness may be introduced. The Phase identifies a point in the life cycle at which
introduction
may occur, while the Note provides a typical scenario related to introduction during the
given
phase.
Phase Note Architecture and Design Such issues could be introduced during hardware architecture and design, then identified later during Testing or System Configuration phases. Implementation Such issues could be introduced during hardware implementation, then identified later during Testing or System Configuration phases.
Applicable PlatformsThis listing shows possible areas for which the given
weakness could appear. These
may be for specific named Languages, Operating Systems, Architectures, Paradigms,
Technologies,
or a class of such platforms. The platform is listed along with how frequently the given
weakness appears for that instance.
Languages Class: Not Language-Specific (Undetermined Prevalence)
Operating Systems Class: Not OS-Specific (Undetermined Prevalence)
Architectures Class: Not Architecture-Specific (Undetermined Prevalence)
Technologies Bus/Interface Hardware (Undetermined Prevalence)
Class: Not Technology-Specific (Undetermined Prevalence)
Weakness Ordinalities Memberships
This MemberOf Relationships table shows additional CWE Categories and Views that
reference this weakness as a member. This information is often useful in understanding where a
weakness fits within the context of external information sources.
Nature Type ID Name MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic.1396 Comprehensive Categorization: Access Control
Vulnerability Mapping Notes Notes
Related Attack Patterns Content
History SubmissionsSubmission Date Submitter Organization 2020-07-17
(CWE 4.2, 2020-08-20)CWE Content Team MITRE 
ModificationsModification Date Modifier Organization 2025-12-11
(CWE 4.19, 2025-12-11)CWE Content Team MITRE updated Weakness_Ordinalities 2023-06-29
(CWE 4.12, 2023-06-29)CWE Content Team MITRE updated Mapping_Notes 2023-04-27
(CWE 4.11, 2023-04-27)CWE Content Team MITRE updated Relationships 2022-06-28
(CWE 4.8, 2022-06-28)CWE Content Team MITRE updated Applicable_Platforms 2022-04-28
(CWE 4.7, 2022-04-28)CWE Content Team MITRE updated Applicable_Platforms, Related_Attack_Patterns 2021-07-20
(CWE 4.5, 2021-07-20)CWE Content Team MITRE updated Related_Attack_Patterns
