| Content by Label | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
Information for Editors |
Risk Assessment Summary
Rule | Severity | Likelihood | Detectable | Repairable | Priority | Level |
|---|---|---|---|---|---|---|
| INT30-C | High | Likely | No | No | P9 | L2 |
| INT31-C | High | Probable | No | Yes | P12 | L1 |
| INT32-C | High | Likely | No | Yes | P18 | L1 |
| INT33-C | Low | Likely | No | Yes | P6 | L2 |
| INT34-C | Low | Unlikely | No | Yes | P2 | L3 |
| INT35-C | Low | Unlikely | No | No | P1 | L3 |
| INT36-C | Low | Probable | Yes | No | P4 | L3 |
Related Rules and Recommendations
| Navigation Map | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Integer values used in the following manner must be guranteed correct:
- As an array index
- In any pointer arithmetic
- As a length or size of an object
- As the bound of an array (for example, a loop counter)
- In security critical code
Recommendations
Use size_t for all integer values representing the size of an object
Rules
Provide adequate range checking
Understand integer conversion rules
Do not make assumptions about the type of a bit-field when used in an expression
Guarantee that integer conversions do not result in lost or misinterpreted data
Guarantee that integer operations do not result in an overflow