...
Tool | Version | Checker | Description |
|---|
| CodeSonar | | (customization) | Users can add a custom check for use of realloc(). |
| Compass/ROSE |
|
| Could detect possible violations of this rule by first flagging any usage of realloc(). Also, it could flag any usage of free that is not preceded by code to clear out the preceding memory, using memset. This heuristic is imperfect because it flags all possible data leaks, not just leaks of "sensitive" data, because ROSE cannot tell which data is sensitive |
| Helix QAC | | C5010 |
|
| LDRA tool suite | | 44 S | Enhanced Enforcement |
| Parasoft C/C++test | | CERT_C-MEM03-a | Sensitive data should be cleared before being deallocated |
| Polyspace Bug Finder | | Include Page |
|---|
| Polyspace Bug Finder_V |
|---|
| Polyspace Bug Finder_V |
|---|
|
| CERT C: Rec. MEM03-C
| Checks for: - Sensitive heap memory not cleared before release
- Uncleared sensitive data in stack
Rec. partially covered. |
| PRQA QAPVS-CStudio | | 5010 | | V1072Partially implemented |
|
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
...
