2339
Notes
Relationship
CWE relationships for this view were obtained by examining the OWASP document and mapping
to any items that were specifically mentioned within the text of a category. As a result, this mapping
is not complete with respect to all of CWE. In addition, some concepts were mentioned in multiple
Top Ten items, which caused them to be mapped to multiple CWE categories. For example, SQL
injection is mentioned in both A1 (CWE-722) and A6 (CWE-727) categories.
Relationship
As of 2008, some parts of CWE were not fully clarified out in terms of weaknesses. When these
areas were mentioned in the OWASP Top Ten, category entries were mapped, although general
mapping practice would usually favor mapping only to weaknesses.
References
[REF-570]"Top 10 2004". 2004 January 7. OWASP. < http://www.owasp.org/index.php/
Top_10_2004 >.
[REF-571]PCI Security Standards Council. "About the PCI Data Security Standard (PCI DSS)". <
https://listings.pcisecuritystandards.org/pci_security/ >.2023-04-07.
Metrics
CWEs in this view Total CWEs
Weaknesses 117 out of 938
Categories 13 out of 374
Views 0 out of 50
Total 130 out of 1362
View-734: Weaknesses Addressed by the CERT C Secure Coding Standard
(2008)
View ID : 734
Type : Graph
Objective
CWE entries in this view (graph) are fully or partially eliminated by following the guidance
presented in the book "The CERT C Secure Coding Standard" published in 2008. This view is
considered obsolete, as a newer version of the coding standard is available. This view statically
represents the coding rules as they were in 2008.
CWE Version 4.14
CWE-734: Weaknesses Addressed by the CERT C Secure Coding Standard (2008)
CWE-734: Weaknesses Addressed by the CERT C Secure Coding Standard (2008)