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

04. Integers (INT)

Created by Robert C. Seacord, last modified by vishal patel on Nov 10, 2010

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

Compare with Current View Page History

Recommendations

Page:

INT00-C. Understand the data model used by your implementation(s)
Page:

INT01-C. Use size_t or rsize_t for all integer values representing the size of an object
Page:

INT02-C. Understand integer conversion rules
Page:

INT04-C. Enforce limits on integer values originating from tainted sources
Page:

INT05-C. Do not use input functions to convert character data if they cannot handle all possible inputs
Page:

INT07-C. Use only explicitly signed or unsigned char type for numeric values
Page:

INT08-C. Verify that all integer values are in range
Page:

INT09-C. Ensure enumeration constants map to unique values
Page:

INT10-C. Do not assume a positive remainder when using the % operator
Page:

INT12-C. Do not make assumptions about the type of a plain int bit-field when used in an expression
Page:

INT13-C. Use bitwise operators only on unsigned operands
Page:

INT14-C. Avoid performing bitwise and arithmetic operations on the same data
Page:

INT15-C. Use intmax_t or uintmax_t for formatted IO on programmer-defined integer types
Page:

INT16-C. Do not make assumptions about representation of signed integers
Page:

INT17-C. Define integer constants in an implementation-independent manner
Page:

INT18-C. Evaluate integer expressions in a larger size before comparing or assigning to that size

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

Rules

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

Risk Assessment Summary

Recommendation	Severity	Likelihood	Remediation Cost	Priority	Level
INT00-C	high	unlikely	high	P3	L3
INT01-C	medium	probable	medium	P8	L2
INT02-C	medium	probable	medium	P8	L2
INT03-C	medium	probable	medium	P8	L2
INT04-C	low	probable	high	P2	L3
INT05-C	medium	probable	high	P4	L3
INT06-C	medium	probable	medium	P8	L2
INT07-C	medium	probable	medium	P8	L2
INT08-C	medium	probable	high	P4	L3
INT09-C	low	probable	medium	P4	L3
INT11-C	low	probable	high	P2	L3
INT12-C	low	unlikely	medium	P2	L3
INT13-C	high	unlikely	medium	P6	L2
INT14-C	medium	unlikely	medium	P4	L3
INT15-C	high	unlikely	medium	P6	L2
INT16-C	medium	unlikely	high	P2	L3
INT17-C	high	probable	low	P18	L1

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	low	medium	P???	L???
INT35-C	high	likely	medium	P18	L1

Related Rules and Recommendations

DCL31-C. Declare identifiers before using them

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

EXP40-C. Do not modify constant values CERT C Secure Coding Standard

No labels