Common Weakness Enumeration

CWE-1000

View Prohibited

Complete Weakness Hierarchy

Status: Draft

This view has a hierarchical organization of all weaknesses within CWE. It is intended to facilitate research into weaknesses, including their inter-dependencies, and can be leveraged to systematically identify theoretical gaps within CWE. It is mainly organized according to abstractions of behaviors and other dimensions instead of how the weaknesses can be detected or mitigated, where they appear in code, or when they are introduced in the development life cycle. By design, this view is expected to include every weakness within CWE.

View entries organize the catalogue and should not be used to map the root cause of a vulnerability.

Mapping guidance

This entry is a View. Views are not weaknesses and therefore inappropriate to describe the root causes of vulnerabilities.

Use this View or other Views to search and navigate for the appropriate weakness.

Relationships and members
Has Member: CWE-284 · View CWE-1000
Has Member: CWE-435 · View CWE-1000
Has Member: CWE-664 · View CWE-1000
Has Member: CWE-682 · View CWE-1000
Has Member: CWE-691 · View CWE-1000
Has Member: CWE-693 · View CWE-1000
Has Member: CWE-697 · View CWE-1000
Has Member: CWE-703 · View CWE-1000
Has Member: CWE-707 · View CWE-1000
Has Member: CWE-710 · View CWE-1000
Notes

Relationship

This view uses a deep hierarchical organization, with more levels of abstraction than other classification schemes. The top-level entries are called Pillars. Where possible, this view uses abstractions that do not consider particular languages, frameworks, technologies, life cycle development phases, frequency of occurrence, or types of resources. It explicitly identifies relationships that form chains and composites, which had not been a formal part of past classification efforts. Chains and composites might help explain why mutual exclusivity is difficult to achieve within security error taxonomies. This view is roughly aligned with CWE's original research into vulnerability theory, especially with respect to behaviors and resources. Ideally, this view will only cover weakness-to-weakness relationships, with minimal overlap and zero groupings. It is expected to include at least one parent/child relationship for every active (non-deprecated) weakness within CWE.

Content history
Submission: CWE Content Team · MITRE · 2008-04-11 · CWE Draft 9
Modification: CWE Content Team · MITRE · 2008-09-08 · CWE 1.0

updated Description, Name, Relationships, View_Audience, View_Structure

Modification: CWE Content Team · MITRE · 2010-02-16 · CWE 1.8

updated Relationships

Modification: CWE Content Team · MITRE · 2018-03-27 · CWE 3.1

updated Description, Other_Notes, View_Audience

Modification: CWE Content Team · MITRE · 2020-02-24 · CWE 4.0

updated Relationships, View_Audience

Modification: CWE Content Team · MITRE · 2021-03-15 · CWE 4.4

updated Description, Other_Notes

Modification: CWE Content Team · MITRE · 2023-06-29 · CWE 4.12

updated Mapping_Notes

Modification: CWE Content Team · MITRE · 2026-10-28 · CWE 5.0

updated Description, Name, Other_Notes, Relationship_Notes, View_Audience

0 vulnerabilities reference this CWE, most recent first.

No vulnerabilities reference this CWE.

No mitigation information available for this CWE.

No CAPEC attack patterns related to this CWE.