Weaknesses in this category are related to rules in the Exceptions and Error Handling (ERR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | V | 868 | Weaknesses Addressed by the SEI CERT C++ Coding Standard (2016 Version) |
| HasMember | Allowed | B | 209 | Generation of Error Message Containing Sensitive Information |
| HasMember | Allowed | B | 390 | Detection of Error Condition Without Action |
| HasMember | Prohibited | B | 391 | Unchecked Error Condition |
| HasMember | Allowed | B | 544 | Missing Standardized Error Handling Mechanism |
| HasMember | Allowed | B | 460 | Improper Cleanup on Thrown Exception |
| HasMember | Allowed | B | 497 | Exposure of Sensitive System Information to an Unauthorized Control Sphere |
| HasMember | Discouraged | P | 703 | Improper Check or Handling of Exceptional Conditions |
| HasMember | Allowed-with-Review | C | 705 | Incorrect Control Flow Scoping |
| HasMember | Allowed-with-Review | C | 754 | Improper Check for Unusual or Exceptional Conditions |
| HasMember | Discouraged | C | 755 | Improper Handling of Exceptional Conditions |
This entry is a Category. Using categories for mapping has been discouraged since 2019. Categories are informal organizational groupings of weaknesses that can help CWE users with data aggregation, navigation, and browsing. However, they are not weaknesses in themselves.
See member weaknesses of this category.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|