Skip to main content
assistive.skiplink.to.breadcrumbs
assistive.skiplink.to.header.menu
assistive.skiplink.to.action.menu
assistive.skiplink.to.quick.search

Rule 04. Integers (INT)

Created by Robert C. Seacord, last modified by Will Snavely on Oct 28, 2016

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Page:

INT30-C. Ensure that unsigned integer operations do not wrap
Page:

INT31-C. Ensure that integer conversions do not result in lost or misinterpreted data
Page:

INT32-C. Ensure that operations on signed integers do not result in overflow
Page:

INT33-C. Ensure that division and remainder operations do not result in divide-by-zero errors
Page:

INT34-C. Do not shift an expression by a negative number of bits or by greater than or equal to the number of bits that exist in the operand
Page:

INT35-C. Use correct integer precisions
Page:

INT36-C. Converting a pointer to integer or integer to pointer

Information for Editors
To have a new guideline automatically listed above be sure to label it int and rule.

Risk Assessment Summary

Rule	Severity	Likelihood	Remediation Cost	Priority	Level
INT30-C	High	Likely	High	P9	L2
INT31-C	High	Probable	High	P6	L2
INT32-C	High	Likely	High	P9	L2
INT33-C	Low	Likely	Medium	P6	L2
INT34-C	Low	Unlikely	Medium	P2	L3
INT35-C	Low	Unlikely	Medium	P2	L3
INT36-C	Low	Probable	High	P2	L3

Related Rules and Recommendations

DCL31-C. Declare identifiers before using them

FIO09-C. Be careful with binary data when transferring data across systems

No labels