2370
Notes
Relationship
The relationships in this view were determined based on specific statements within the rules from
the standard. Not all rules have direct relationships to individual weaknesses, although they likely
have chaining relationships in specific circumstances.
References
[REF-813]Fred Long, Dhruv Mohindra, Robert C. Seacord, Dean F. Sutherland and David
Svoboda. "The CERT Oracle Coding Standard for Java". 1st Edition. 2011 September 8. Addison-
Wesley Professional.
Metrics
CWEs in this view Total CWEs
Weaknesses 104 out of 938
Categories 17 out of 374
Views 0 out of 50
Total 121 out of 1362
View-868: Weaknesses Addressed by the SEI CERT C++ Coding Standard
(2016 Version)
View ID : 868
Type : Graph
Objective
CWE entries in this view (graph) are fully or partially eliminated by following the SEI CERT C++
Coding Standard, as published in 2016. This view is no longer being actively maintained, since it
statically represents the coding rules as they were in 2016.
Audience
Software Developers
By following the CERT C++ Secure Coding Standard, developers will be able to fully or partially
prevent the weaknesses that are identified in this view. In addition, developers can use a
CWE coverage graph to determine which weaknesses are not directly addressed by the
standard, which will help identify and resolve remaining gaps in training, tool acquisition, or other
approaches for reducing weaknesses.
Product Customers
If a software developer claims to be following the CERT C++ Secure Coding Standard, 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 link them to the relevant Secure Coding Standard.
Membership
Nature Type ID Name Page
HasMember 869 CERT C++ Secure Coding Section 01 - Preprocessor (PRE) 2373
CWE Version 4.14
CWE-884: CWE Cross-section
CWE-884: CWE Cross-section