Title: BB. Definitions  
Author: Admin Jul 28, 2006
Last Changed by: Robert Schiela Jan 15, 2019
Tiny Link: (useful for email) https://wiki.sei.cmu.edu/confluence/x/kdYxBQ
Export As: Word · PDF  
Incoming Links
SEI CERT C Coding Standard (269)
    Page: PRE11-C. Do not conclude macro definitions with a semicolon
    Page: ENV02-C. Beware of multiple environment variables with the same effective name
    Page: FIO37-C. Do not assume that fgets() or fgetws() returns a nonempty string when successful
    Page: ARR32-C. Ensure size arguments for variable length arrays are in a valid range
    Page: MSC21-C. Use robust loop termination conditions
    Page: DCL39-C. Avoid information leakage when passing a structure across a trust boundary
    Page: MSC14-C. Do not introduce unnecessary platform dependencies
    Page: API09-C. Compatible values should have the same type
    Page: ARR37-C. Do not add or subtract an integer to a pointer to a non-array object
    Page: MSC06-C. Beware of compiler optimizations
    Page: PRE05-C. Understand macro replacement when concatenating tokens or performing stringification
    Page: SIG35-C. Do not return from a computational exception signal handler
    Page: DCL05-C. Use typedefs of non-pointer types only
    Page: MSC24-C. Do not use deprecated or obsolescent functions
    Page: API02-C. Functions that read or write to or from an array should take an argument to specify the source or target size
    Page: CON34-C. Declare objects shared between threads with appropriate storage durations
    Page: EXP42-C. Do not compare padding data
    Page: MSC09-C. Character encoding: Use subset of ASCII for safety
    Page: SIG31-C. Do not access shared objects in signal handlers
    Page: CON09-C. Avoid the ABA problem when using lock-free algorithms
    Page: FIO20-C. Avoid unintentional truncation when using fgets() or fgetws()
    Page: MSC10-C. Character encoding: UTF8-related issues
    Page: INT04-C. Enforce limits on integer values originating from tainted sources
    Page: CON35-C. Avoid deadlock by locking in a predefined order
    Page: INT09-C. Ensure enumeration constants map to unique values
    Page: DCL02-C. Use visually distinct identifiers
    Page: MSC11-C. Incorporate diagnostic tests using assertions
    Page: EXP11-C. Do not make assumptions regarding the layout of structures with bit-fields
    Page: WIN04-C. Consider encrypting function pointers
    Page: PRE02-C. Macro replacement lists should be parenthesized
    Page: Scope
    Page: INT13-C. Use bitwise operators only on unsigned operands
    Page: STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator
    Page: STR30-C. Do not attempt to modify string literals
    Page: MEM11-C. Do not assume infinite heap space
    Page: SIG02-C. Avoid using signals to implement normal functionality
    Page: DCL20-C. Explicitly specify void when a function accepts no arguments
    Page: SIG34-C. Do not call signal() from within interruptible signal handlers
    Page: CON32-C. Prevent data races when accessing bit-fields from multiple threads
    Page: DCL12-C. Implement abstract data types using opaque types
    Page: ERR05-C. Application-independent code should provide error detection without dictating error handling
    Page: DCL13-C. Declare function parameters that are pointers to values not changed by the function as const
    Page: ENV34-C. Do not store pointers returned by certain functions
    Page: FIO21-C. Do not create temporary files in shared directories
    Page: INT32-C. Ensure that operations on signed integers do not result in overflow
    Page: MEM00-C. Allocate and free memory in the same module, at the same level of abstraction
    Page: FIO22-C. Close files before spawning processes
    Page: PRE31-C. Avoid side effects in arguments to unsafe macros
    Page: EXP44-C. Do not rely on side effects in operands to sizeof, _Alignof, or _Generic
    Page: STR05-C. Use pointers to const when referring to string literals
    Page: FIO14-C. Understand the difference between text mode and binary mode with file streams
    Page: FIO42-C. Close files when they are no longer needed
    Page: EXP36-C. Do not cast pointers into more strictly aligned pointer types
    Page: EXP45-C. Do not perform assignments in selection statements
    Page: WIN30-C. Properly pair allocation and deallocation functions
    Page: FIO32-C. Do not perform operations on devices that are only appropriate for files
    Page: POS47-C. Do not use threads that can be canceled asynchronously
    Page: STR10-C. Do not concatenate different type of string literals
    Page: API08-C. Avoid parameter names in a function prototype
    Page: PRE07-C. Avoid using repeated question marks
    Page: ERR00-C. Adopt and implement a consistent and comprehensive error-handling policy
    Page: INT02-C. Understand integer conversion rules
    Page: Rule 51. Microsoft Windows (WIN)
    Page: STR38-C. Do not confuse narrow and wide character strings and functions
    Page: PRE04-C. Do not reuse a standard header file name
    Page: STR04-C. Use plain char for characters in the basic character set
    Page: DCL15-C. Declare file-scope objects or functions that do not need external linkage as static
    Page: EXP43-C. Avoid undefined behavior when using restrict-qualified pointers
    Page: Conformance Testing
    Page: POS54-C. Detect and handle POSIX library errors
    Page: FIO41-C. Do not call getc(), putc(), getwc(), or putwc() with a stream argument that has side effects
    Page: ARR30-C. Do not form or use out-of-bounds pointers or array subscripts
    Page: EXP35-C. Do not modify objects with temporary lifetime
    Page: MSC07-C. Detect and remove dead code
    Page: FIO30-C. Exclude user input from format strings
    Page: CON33-C. Avoid race conditions when using library functions
    Page: DCL19-C. Minimize the scope of variables and functions
    Page: EXP05-C. Do not cast away a const qualification
    Page: MEM06-C. Ensure that sensitive data is not written out to disk
    Page: API05-C. Use conformant array parameters
    Page: MSC33-C. Do not pass invalid data to the asctime() function
    Page: ARR00-C. Understand how arrays work
    Page: FLP36-C. Preserve precision when converting integral values to floating-point type
    Page: INT00-C. Understand the data model used by your implementation(s)
    Page: FLP01-C. Take care in rearranging floating-point expressions
    Page: EXP40-C. Do not modify constant objects
    Page: ARR39-C. Do not add or subtract a scaled integer to a pointer
    Page: FLP04-C. Check floating-point inputs for exceptional values
    Page: DCL30-C. Declare objects with appropriate storage durations
    Page: INT15-C. Use intmax_t or uintmax_t for formatted IO on programmer-defined integer types
    Page: DCL16-C. Use "L," not "l," to indicate a long value
    Page: STR00-C. Represent characters using an appropriate type
    Page: EXP08-C. Ensure pointer arithmetic is used correctly
    Page: PRE00-C. Prefer inline or static functions to function-like macros
    Page: CON38-C. Preserve thread safety and liveness when using condition variables
    Page: FLP34-C. Ensure that floating-point conversions are within range of the new type
    Page: CON39-C. Do not join or detach a thread that was previously joined or detached
    Page: EXP37-C. Call functions with the correct number and type of arguments
    Page: DCL41-C. Do not declare variables inside a switch statement before the first case label
    Page: POS53-C. Do not use more than one mutex for concurrent waiting operations on a condition variable
    Page: MEM34-C. Only free memory allocated dynamically
    Page: CON07-C. Ensure that compound operations on shared variables are atomic
    Page: STR02-C. Sanitize data passed to complex subsystems
    Page: DCL11-C. Understand the type issues associated with variadic functions
    Page: INT05-C. Do not use input functions to convert character data if they cannot handle all possible inputs
    Page: MEM05-C. Avoid large stack allocations
    Page: MSC38-C. Do not treat a predefined identifier as an object if it might only be implemented as a macro
    Page: FIO44-C. Only use values for fsetpos() that are returned from fgetpos()
    Page: DCL09-C. Declare functions that return errno with a return type of errno_t
    Page: STR37-C. Arguments to character-handling functions must be representable as an unsigned char
    Page: DCL10-C. Maintain the contract between the writer and caller of variadic functions
    Page: DCL21-C. Understand the storage of compound literals
    Page: EXP09-C. Use sizeof to determine the size of a type or variable
    Page: API04-C. Provide a consistent and usable error-checking mechanism
    Page: FLP32-C. Prevent or detect domain and range errors in math functions
    Page: EXP20-C. Perform explicit tests to determine success, true and false, and equality
    Page: CON37-C. Do not call signal() in a multithreaded program
    Page: STR07-C. Use the bounds-checking interfaces for string manipulation
    Page: DCL36-C. Do not declare an identifier with conflicting linkage classifications
    Page: FIO02-C. Canonicalize path names originating from tainted sources
    Page: DCL08-C. Properly encode relationships in constant definitions
    Page: MSC19-C. For functions that return an array, prefer returning an empty array over a null value
    Page: INT14-C. Avoid performing bitwise and arithmetic operations on the same data
    Page: DCL17-C. Beware of miscompiled volatile-qualified variables
    Page: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction
    Page: CON36-C. Wrap functions that can spuriously wake up in a loop
    Page: ERR03-C. Use runtime-constraint handlers when calling the bounds-checking interfaces
    Page: PRE32-C. Do not use preprocessor directives in invocations of function-like macros
    Page: Undefined and implementation-defined behaviors not deemed ruleworthy
    Page: STR11-C. Do not specify the bound of a character array initialized with a string literal
    Page: API03-C. Create consistent interfaces and capabilities across related functions
    Page: FIO01-C. Be careful using functions that use file names for identification
    Page: POS44-C. Do not use signals to terminate threads
    Page: FLP03-C. Detect and handle floating-point errors
    Page: CON30-C. Clean up thread-specific storage
    Page: ENV32-C. All exit handlers must return normally
    Page: FIO38-C. Do not copy a FILE object
    Page: MEM03-C. Clear sensitive information stored in reusable resources
    Page: INT16-C. Do not make assumptions about representation of signed integers
    Page: ARR36-C. Do not subtract or compare two pointers that do not refer to the same array
    Page: EXP07-C. Do not diminish the benefits of constants by assuming their values in expressions
    Page: MEM07-C. Ensure that the arguments to calloc(), when multiplied, do not wrap
    Page: PRE06-C. Enclose header files in an include guard
    Page: MEM01-C. Store a new value in pointers immediately after free()
    Page: ARR38-C. Guarantee that library functions do not form invalid pointers
    Page: PRE10-C. Wrap multistatement macros in a do-while loop
    Page: PRE30-C. Do not create a universal character name through concatenation
    Page: MSC23-C. Beware of vendor-specific library and language differences
    Page: FIO39-C. Do not alternately input and output from a stream without an intervening flush or positioning call
    Page: FLP07-C. Cast the return value of a function that returns a floating-point type
    Page: FIO45-C. Avoid TOCTOU race conditions while accessing files
    Page: FLP37-C. Do not use object representations to compare floating-point values
    Page: ERR34-C. Detect errors when converting a string to a number
    Page: MSC18-C. Be careful while handling sensitive data, such as passwords, in program code
    Page: POS33-C. Do not use vfork()
    Page: INT07-C. Use only explicitly signed or unsigned char type for numeric values
    Page: STR03-C. Do not inadvertently truncate a string
    Page: FIO08-C. Take care when calling remove() on an open file
    Page: PRE12-C. Do not define unsafe macros
    Page: CON43-C. Do not allow data races in multithreaded code
    Page: PRE08-C. Guarantee that header file names are unique
    Page: DCL22-C. Use volatile for data that cannot be cached
    Page: SIG30-C. Call only asynchronous-safe functions within signal handlers
    Page: FLP30-C. Do not use floating-point variables as loop counters
    Page: Rules versus Recommendations
    Page: MEM35-C. Allocate sufficient memory for an object
    Page: INT30-C. Ensure that unsigned integer operations do not wrap
    Page: EXP02-C. Be aware of the short-circuit behavior of the logical AND and OR operators
    Page: INT08-C. Verify that all integer values are in range
    Page: MSC05-C. Do not manipulate time_t typed values directly
    Page: FIO40-C. Reset strings on fgets() or fgetws() failure
    Page: STR08-C. Use managed strings for development of new string manipulation code
    Page: FIO10-C. Take care when using the rename() function
    Page: ERR04-C. Choose an appropriate termination strategy
    Page: DCL40-C. Do not create incompatible declarations of the same function or object
    Page: EXP10-C. Do not depend on the order of evaluation of subexpressions or the order in which side effects take place
    Page: MSC04-C. Use comments consistently and in a readable fashion
    Page: ERR07-C. Prefer functions that support error checking over equivalent functions that don't
    Page: INT33-C. Ensure that division and remainder operations do not result in divide-by-zero errors
    Page: MSC00-C. Compile cleanly at high warning levels
    Page: ERR06-C. Understand the termination behavior of assert() and abort()
    Page: ERR33-C. Detect and handle standard library errors
    Page: MEM04-C. Beware of zero-length allocations
    Page: PRE13-C. Use the Standard predefined macros to test for versions and features.
    Page: DCL37-C. Do not declare or define a reserved identifier
    Page: Taint Analysis
    Page: INT36-C. Converting a pointer to integer or integer to pointer
    Page: How this Coding Standard is Organized
    Page: SIG00-C. Mask signals handled by noninterruptible signal handlers
    Page: DCL03-C. Use a static assertion to test the value of a constant expression
    Page: DCL07-C. Include the appropriate type information in function declarators
    Page: API07-C. Enforce type safety
    Page: MSC32-C. Properly seed pseudorandom number generators
    Page: EXP39-C. Do not access a variable through a pointer of an incompatible type
    Page: EXP32-C. Do not access a volatile object through a nonvolatile reference
    Page: FIO15-C. Ensure that file operations are performed in a secure directory
    Page: DCL04-C. Do not declare more than one variable per declaration
    Page: PRE01-C. Use parentheses within macros around parameter names
    Page: FIO46-C. Do not access a closed file
    Page: Rec. 51. Microsoft Windows (WIN)
    Page: MSC30-C. Do not use the rand() function for generating pseudorandom numbers
    Page: FIO47-C. Use valid format strings
    Page: INT01-C. Use rsize_t or size_t for all integer values representing the size of an object
    Page: MEM02-C. Immediately cast the result of a memory allocation function call into a pointer to the allocated type
    Page: DCL23-C. Guarantee that mutually visible identifiers are unique
    Page: ERR02-C. Avoid in-band error indicators
    Page: MSC12-C. Detect and remove code that has no effect or is never executed
    Page: System Qualities
    Page: DD. Unspecified Behavior
    Page: FIO24-C. Do not open a file that is already open
    Page: ENV03-C. Sanitize the environment when invoking external programs
    Page: MEM33-C. Allocate and copy structures containing a flexible array member dynamically
    Page: EXP34-C. Do not dereference null pointers
    Page: API00-C. Functions should validate their parameters
    Page: CON04-C. Join or detach threads even if their exit status is unimportant
    Page: ENV31-C. Do not rely on an environment pointer following an operation that may invalidate it
    Page: DCL31-C. Declare identifiers before using them
    Page: STR32-C. Do not pass a non-null-terminated character sequence to a library function that expects a string
    Page: CON05-C. Do not perform operations that can block while holding a lock
    Page: MSC01-C. Strive for logical completeness
    Page: DCL00-C. Const-qualify immutable objects
    Page: FIO17-C. Do not rely on an ending null character when using fread()
    Page: ENV30-C. Do not modify the object referenced by the return value of certain functions
    Page: ERR30-C. Set errno to zero before calling a library function known to set errno, and check errno only after the function returns a value indicating failure
    Page: EXP00-C. Use parentheses for precedence of operation
    Page: INT10-C. Do not assume a positive remainder when using the % operator
    Page: MSC22-C. Use the setjmp(), longjmp() facility securely
    Page: MEM10-C. Define and use a pointer validation function
    Page: INT17-C. Define integer constants in an implementation-independent manner
    Page: SIG01-C. Understand implementation-specific details regarding signal handler persistence
    Page: POS02-C. Follow the principle of least privilege
    Page: ENV33-C. Do not call system()
    Page: STR01-C. Adopt and implement a consistent plan for managing strings
    Page: EXP12-C. Do not ignore values returned by functions
    Page: EXP16-C. Do not compare function pointers to constant values
    Page: FLP05-C. Do not use denormalized numbers
    Page: FIO03-C. Do not make assumptions about fopen() and file creation
    Page: ERR32-C. Do not rely on indeterminate values of errno
    Page: PRE03-C. Prefer typedefs to defines for encoding non-pointer types
    Page: MSC39-C. Do not call va_arg() on a va_list that has an indeterminate value
    Page: CC. Undefined Behavior
    Page: FIO05-C. Identify files using multiple file attributes
    Page: EXP33-C. Do not read uninitialized memory
    Page: EXP47-C. Do not call va_arg with an argument of the incorrect type
    Page: FIO34-C. Distinguish between characters read from a file and EOF or WEOF
    Page: EXP03-C. Do not assume the size of a structure is the sum of the sizes of its members
    Page: MEM31-C. Free dynamically allocated memory when no longer needed
    Page: FIO06-C. Create files with appropriate access permissions
    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: MSC37-C. Ensure that control never reaches the end of a non-void function
    Page: DCL38-C. Use the correct syntax when declaring a flexible array member
    Page: ENV01-C. Do not make assumptions about the size of an environment variable
    Page: MSC13-C. Detect and remove unused values
    Page: MEM36-C. Do not modify the alignment of objects by calling realloc()
    Page: MSC15-C. Do not depend on undefined behavior
    Page: POS51-C. Avoid deadlock with POSIX threads by locking in predefined order
    Page: MSC40-C. Do not violate constraints
    Page: MEM30-C. Do not access freed memory
    Page: FLP00-C. Understand the limitations of floating-point numbers
    Page: EXP30-C. Do not depend on the order of evaluation for side effects
    Page: INT12-C. Do not make assumptions about the type of a plain int bit-field when used in an expression
    Page: STR34-C. Cast characters to unsigned char before converting to larger integer sizes
    Page: FIO11-C. Take care when specifying the mode parameter of fopen()
    Page: INT31-C. Ensure that integer conversions do not result in lost or misinterpreted data
    Page: DCL06-C. Use meaningful symbolic constants to represent literal values
    Page: CON31-C. Do not destroy a mutex while it is locked
    Page: ERR01-C. Use ferror() rather than errno to check for FILE stream errors
    Page: FIO19-C. Do not use fseek() and ftell() to compute the size of a regular file
    Page: INT18-C. Evaluate integer expressions in a larger size before comparing or assigning to that size
CERT Secure Coding (1)
    Page: Top 10 Secure Coding Practices
Android (1)
    Page: Rules versus Recommendations
SEI CERT C++ Coding Standard (9)
    Page: EXP60-CPP. Do not pass a nonstandard-layout type object across execution boundaries
    Page: OOP54-CPP. Gracefully handle self-copy assignment
    Page: DCL50-CPP. Do not define a C-style variadic function
    Page: EXP63-CPP. Do not rely on the value of a moved-from object
    Page: MEM56-CPP. Do not store an already-owned pointer value in an unrelated smart pointer
    Page: EXP50-CPP. Do not depend on the order of evaluation for side effects
    Page: MEM50-CPP. Do not access freed memory
    Page: ERR59-CPP. Do not throw an exception across execution boundaries
    Page: FIO50-CPP. Do not alternately input and output from a file stream without an intervening positioning call
Hierarchy
Parent Page
    Page: 4 Back Matter
Labels
Global Labels (2)
Time Editor  
Jan 15, 2019 18:54 Robert Schiela View Changes
Corrected reference for "analyzer" definition to TS 17961, instead of 9899:2011, which was incorrect.
Jul 28, 2016 12:38 Sandy Shrum View Changes
Jun 14, 2016 10:26 Aaron Ballman View Changes
Removing definition of mutilated value because it is never used anywhere.
Feb 11, 2016 11:14 David Keaton View Changes
Fixed incorrect definition of critical sections.
Feb 10, 2016 17:16 Will Snavely