...
Race conditions caused by multiple threads invoking the same library function can lead to abnormal termination of the application, data integrity violations, or a denial-of-service attack.
Rule | Severity | Likelihood | Detectable | RepairableRemediation Cost | Priority | Level |
|---|---|---|---|---|---|---|
CON33-C | Medium | Probable | No | NoHigh | P4 | L3 |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
...
Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Astrée |
| Supported, but no explicit checker | |||||||
| CodeSonar |
| BADFUNC.RANDOM.RAND | Use of | ||||||
| Compass/ROSE | A module written in Compass/ROSE can detect violations of this rule | ||||||||
| Cppcheck Premium |
| premium-cert-con33-c | |||||||
| Helix QAC |
| C5037 C++5021 DF4976, DF4977 | |||||||
| Klocwork |
| CERT.CONC.LIB_FUNC_USE | |||||||
| LDRA tool suite |
| 44 S | Partially Implemented | ||||||
| Parasoft C/C++test |
| CERT_C-CON33-a | Avoid using thread-unsafe functions | ||||||
| PC-lint Plus |
| 586 | Fully supported | ||||||
| CERT C: Rule CON33-C | Checks for data race through standard library function call (rule fully covered) |
Related Guidelines
Key here (explains table format and definitions)
...