...
On implementations that do not detect output-string-length overflow, it is possible to overflow the output buffers.
Rule | Severity | Likelihood | Detectable | RepairableRemediation Cost | Priority | Level |
|---|---|---|---|---|---|---|
MSC33-C | High | Likely | No | NoLow | P27P9 | L1L2 |
Automated Detection
Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Astrée |
| Supported, but no explicit checker | |||||||
| Axivion Bauhaus Suite |
| CertC-MSC33 | |||||||
| CodeSonar |
| BADFUNC.TIME_H | Use of <time.h> Time/Date Function | ||||||
| Cppcheck Premium |
| premium-cert-msc33-c | |||||||
| Helix QAC |
| C5032 C++5030 | |||||||
| Klocwork |
| CERT.MSC.ASCTIME | |||||||
| LDRA tool suite |
| 44 S | Enhanced Enforcement | ||||||
| Parasoft C/C++test |
| CERT_C-MSC33-a | The 'asctime()' and 'asctime_r()' functions should not be used | ||||||
| PC-lint Plus |
| 586 | Fully supported | ||||||
| Polyspace Bug Finder |
| CERT C: Rule MSC33-C | Checks for use of obsolete standard function (rule partially covered) | ||||||
| RuleChecker |
| Supported, but no explicit checker |
...