...
Failure to provide a consistent and usable error-checking mechanism can result in type errors in the program.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
API04-C | Medium | Unlikely | Medium | P4 | L3 |
Automated Detection
Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Polyspace Bug Finder |
| CERT C: Rec. API04-C | Checks for situations where returned value of a sensitive function is not checked (rule partially covered) |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
Key here (explains table format and definitions)
Taxonomy | Taxonomy item | Relationship |
|---|---|---|
| ISO/IEC 9945:2003 |
| Prior to 2018-01-12: CERT: Unspecified Relationship | |
| ISO/IEC 23360-1:2006 |
| Prior to 2018-01-12: CERT: Unspecified Relationship | |
| ISO/IEC TR 24731-1 |
| Prior to 2018-01-12: CERT: Unspecified Relationship | |
| ISO/IEC TR 24731-2 |
| Prior to 2018-01-12: CERT: Unspecified Relationship | ||
| MISRA C:2012 | Rule 21.3 (required) | Prior to 2018-01-12: CERT: Unspecified Relationship |
| MISRA C:2012 | Directive 4.12 (required) |
| Prior to 2018-01-12: CERT: Unspecified Relationship | ||
| CWE 2.11 | CWE-754, Improper check for unusual or exceptional conditions | Prior to 2018-01-12: CERT: |
Bibliography
...
...