|
|
|
|
CWE-750: Weaknesses in the 2009 CWE/SANS Top 25 Most Dangerous Programming Errors | |
| | Weaknesses in the 2009 CWE/SANS Top 25 Most Dangerous Programming Errors |
Definition in a New Window
|
| View ID: 750 (View: Graph) | | Status: Incomplete |
View Data View Objective
CWE entries in this view (graph) are listed in the 2009 CWE/SANS Top 25
Programming Errors.
View Metrics | CWEs in this view | | Total CWEs |
|---|
| Total | 28 | out of | 791 | | Views | 0 | out of | 22 | | Categories | 3 | out of | 106 | | Weaknesses | 23 | out of | 651 | | Compound_Elements | 2 | out of | 12 |
View Audience | Stakeholder | Description |
| Developers | By following the Top 25, developers will be able to significantly
reduce the number of weaknesses that occur in their software. |
| Software Customers | If a software developer claims to be following the Top 25, then
customers can search for the weaknesses in this view in order to
formulate independent evidence of that claim. |
| Educators | Educators can use this view in multiple ways. For example, if there is
a focus on teaching weaknesses, the educator could focus on the Top
25. |
Relationships | Nature | Type | ID | Name | View(s) this relationship pertains to |
| HasMember | Category | 751 | Insecure Interaction Between Components | Weaknesses in the 2009 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)750 | | HasMember | Category | 752 | Risky Resource Management | Weaknesses in the 2009 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)750 | | HasMember | Category | 753 | Porous Defenses | Weaknesses in the 2009 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)750 |
References Content History | Submissions |
|---|
| Submission Date | Submitter | Organization | Source |
|---|
| 2009-01-12 | | | Internal CWE Team | |
|