...
Failing to free thread-specific objects results in memory leaks and could result in a denial-of-service attack.
Rule | Severity | Likelihood | Detectable | RepairableRemediation Cost | Priority | Level |
|---|---|---|---|---|---|---|
CON30-C | Medium | Unlikely | No | MediumNo | P4P2 | L3 |
Automated Detection
| Tool | Version | Checker | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Astrée |
| Supported, but no explicit checker | |||||||||||
| CodeSonar |
| ALLOC.LEAK | Leak | ||||||||||
| Coverity |
| ALLOC_FREE_MISMATCH | Partially implemented, correct implementation is more involved | ||||||||||
| Cppcheck Premium |
| premium-cert-con30-c | |||||||||||
| Helix QAC |
| C1780, C1781, C1782, C1783, C1784 | |||||||||||
| Parasoft C/C++test |
| CERT_C-CON30-a | Ensure resources are freed | ||||||||||
| CERT C: Rule CON30-C | Checks for thread-specific memory leak (rule fully covered) | Helix QAC | ||||||||||
| Include Page | Helix QAC_V | Helix QAC_V
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
...