...
Defining an unsafe macro leads to invocations of the macro with an argument that has side effects, causing those side effects to occur more than once. Unexpected or undefined program behavior can result.
Rule | Severity | Likelihood | Detectable | RepairableRemediation Cost | Priority | Level |
|---|---|---|---|---|---|---|
PRE12-C | Low | Probable | Yes | NoLow | P6P4 | L2L3 |
Automated Detection
| Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Astrée |
| macro-parameter-multiplied macro-parameter-unused | Partially checked | ||||||
| Axivion Bauhaus Suite |
| CertC-PRE12 | |||||||
| CC2.PRE12 | Fully implemented | |||||||
| Helix QAC |
| C3456 | |||||||
| LDRA tool suite |
| 562 S, 572 S, 35 D, 1 Q | Partially implemented | ||||||
| RuleChecker |
| macro-parameter-multiplied macro-parameter-unused | Partially checked |
...
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
...