The Cert C Coding Standard : 98 Rules for Developing Safe, Reliable, and Secure Systems (Sei Series in Software Engineering) （2ND）

Seacord, Robert C.

Addison-Wesley Professional（2014/05発売）

• 製本 Paperback:紙装版/ペーパーバック版／ページ数 517 p.
• 言語 ENG
• 商品コード 9780321984043
• DDC分類 005.133

Full Description

"At Cisco, we have adopted the CERT C Coding Standard as the internal secure coding standard for all C developers. It is a core component of our secure development lifecycle. The coding standard described in this book breaks down complex software security topics into easy-to-follow rules with excellent real-world examples. It is an essential reference for any developer who wishes to write secure and resilient software in C and C++."-Edward D. Paradise, vice president, engineering, threat response, intelligence, and development, Cisco SystemsSecure programming in C can be more difficult than even many experienced programmers realize. To help programmers write more secure code, The CERT (R) C Coding Standard, Second Edition, fully documents the second official release of the CERT standard for secure coding in C. The rules laid forth in this new edition will help ensure that programmers' code fully complies with the new C11 standard; it also addresses earlier versions, including C99. The new standard itemizes those coding errors that are the root causes of current software vulnerabilities in C, prioritizing them by severity, likelihood of exploitation, and remediation costs. Each of the text's 98 guidelines includes examples of insecure code as well as secure, C11-conforming, alternative implementations. If uniformly applied, these guidelines will eliminate critical coding errors that lead to buffer overflows, format-string vulnerabilities, integer overflow, and other common vulnerabilities.This book reflects numerous experts' contributions to the open development and review of the rules and recommendations that comprise this standard.Coverage includesPreprocessor Declarations and Initialization Expressions Integers Floating Point Arrays Characters and Strings Memory Management Input/Output Environment Signals Error Handling Concurrency Miscellaneous Issues

Contents

Preface xiiiAcknowledgments xxxviiContributors xxxixAbout the Author xliiiChapter 1: Preprocessor (PRE) 1PRE30-C. Do not create a universal character name through concatenation 2PRE31-C. Avoid side effects in arguments to unsafe macros 3PRE32-C. Do not use preprocessor directives in invocations of function-like macros 8Chapter 2: Declarations and Initialization (DCL) 11DCL30-C. Declare objects with appropriate storage durations 12DCL31-C. Declare identifiers before using them 16DCL36-C. Do not declare an identifier with conflicting linkage classifications 20DCL37-C. Do not declare or define a reserved identifier 23DCL38-C. Use the correct syntax when declaring a flexible array member 29DCL39-C. Avoid information leakage in structure padding 32DCL40-C. Do not create incompatible declarations of the same function or object 37DCL41-C. Do not declare variables inside a switch statement before the first case label 43Chapter 3: Expressions (EXP) 47EXP30-C. Do not depend on the order of evaluation for side effects 48EXP32-C. Do not access a volatile object through a nonvolatile reference 54EXP33-C. Do not read uninitialized memory 56EXP34-C. Do not dereference null pointers 65EXP35-C. Do not modify objects with temporary lifetime 70EXP36-C. Do not cast pointers into more strictly aligned pointer types 73EXP37-C. Call functions with the correct number and type of arguments 77EXP39-C. Do not access a variable through a pointer of an incompatible type 83EXP40-C. Do not modify constant objects 89EXP42-C. Do not compare padding data 91EXP43-C. Avoid undefined behavior when using restrict-qualified pointers 93EXP44-C. Do not rely on side effects in operands to sizeof, _Alignof, or _Generic 102EXP45-C. Do not perform assignments in selection statements 105Chapter 4: Integers (INT) 111INT30-C. Ensure that unsigned integer operations do not wrap 112INT31-C. Ensure that integer conversions do not result in lost or misinterpreted data 118INT32-C. Ensure that operations on signed integers do not result in overflow 126INT33-C. Ensure that division and remainder operations do not result in divide-by-zero errors 135INT34-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 138INT35-C. Use correct integer precisions 143INT36-C. Converting a pointer to integer or integer to pointer 145Chapter 5: Floating Point (FLP) 151FLP30-C. Do not use floating-point variables as loop counters 152FLP32-C. Prevent or detect domain and range errors in math functions 154FLP34-C. Ensure that floating-point conversions are within range of the new type 163FLP36-C. Preserve precision when converting integral values to floating-point type 166Chapter 6: Arrays (ARR) 169ARR30-C. Do not form or use out-of-bounds pointers or array subscripts 170ARR32-C. Ensure size arguments for variable length arrays are in a valid range 180ARR36-C. Do not subtract or compare two pointers that do not refer to the same array 182ARR37-C. Do not add or subtract an integer to a pointer to a non-array object 184ARR38-C. Guarantee that library functions do not form invalid pointers 187ARR39-C. Do not add or subtract a scaled integer to a pointer 196Chapter 7: Characters and Strings (STR) 201STR30-C. Do not attempt to modify string literals 202STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator 205STR32-C. Do not pass a non-null-terminated character sequence to a library function that expects a string 218STR34-C. Cast characters to unsigned char before converting to larger integer sizes 223STR37-C. Arguments to character handling functions must be representable as an unsigned char 227STR38-C. Do not confuse narrow and wide character strings and functions 229Chapter 8: Memory Management (MEM) 233MEM30-C. Do not access freed memory 234MEM31-C. Free dynamically allocated memory when no longer needed 239MEM33-C. Allocate and copy structures containing a flexible array member dynamically 241MEM34-C. Only free memory allocated dynamically 246MEM35-C. Allocate sufficient memory for an object 250MEM36-C. Do not modify the alignment of objects by calling realloc() 253Chapter 9: Input/Output (FIO) 257FIO30-C. Exclude user input from format strings 258FIO31-C. Do not open a file that is already open 263FIO32-C. Do not perform operations on devices that are only appropriate for files 265FIO34-C. Distinguish between characters read from a file and EOF or WEOF 272FIO37-C. Do not assume that fgets() or fgetws() returns a nonempty string when successful 277FIO38-C. Do not copy a FILE object 279FIO39-C. Do not alternately input and output from a stream without an intervening flush or positioning call 280FIO40-C. Reset strings on fgets() or fgetws() failure 283FIO41-C. Do not call getc(), putc(), getwc(), or putwc() with a stream argument that has side effects 284FIO42-C. Close files when they are no longer needed 288FIO44-C. Only use values for fsetpos() that are returned from fgetpos() 292FIO45-C. Avoid TOCTOU race conditions while accessing files 294FIO46-C. Do not access a closed file 298FIO47-C. Use valid format strings 299Chapter 10: Environment (ENV) 305ENV30-C. Do not modify the object referenced by the return value of certain functions 306ENV31-C. Do not rely on an environment pointer following an operation that may invalidate it 311ENV32-C. All exit handlers must return normally 315ENV33-C. Do not call system() 319ENV34-C. Do not store pointers returned by certain functions 325Chapter 11: Signals (SIG) 333SIG30-C. Call only asynchronous-safe functions within signal handlers 334SIG31-C. Do not access shared objects in signal handlers 342SIG34-C. Do not call signal() from within interruptible signal handlers 345SIG35-C. Do not return from a computational exception signal handler 349Chapter 12: Error Handling (ERR) 353ERR30-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 354ERR32-C. Do not rely on indeterminate values of errno 361ERR33-C. Detect and handle standard library errors 365Chapter 13: Concurrency (CON) 383CON30-C. Clean up thread-specific storage 384CON31-C. Do not destroy a mutex while it is locked 388CON32-C. Prevent data races when accessing bit-fields from multiple threads 391CON33-C. Avoid race conditions when using library functions 394CON34-C. Declare objects shared between threads with appropriate storage durations 398CON35-C. Avoid deadlock by locking in a predefined order 406CON36-C. Wrap functions that can spuriously wake up in a loop 411CON37-C. Do not call signal() in a multithreaded program 414CON38-C. Preserve thread-safety and liveness when using condition variables 416CON39-C. Do not join or detach a thread that was previously joined or detached 424CON40-C. Do not refer to an atomic variable twice in an expression 426CON41-C. Wrap functions that can fail spuriously in a loop 430Chapter 14: Miscellaneous (MSC) 435MSC30-C. Do not use the rand() function for generating pseudorandom numbers 436MSC32-C. Properly seed pseudorandom number generators 439MSC33-C. Do not pass invalid data to the asctime() function 443MSC37-C. Ensure that control never reaches the end of a non-void function 446MSC38-C. Do not treat a predefined identifier as an object if it might only be implemented as a macro 449MSC39-C. Do not call va_arg() on a va_list that has an indeterminate value 451MSC40-C. Do not violate constraints 453Appendix A: Glossary 459Appendix B: Undefined Behavior 465Appendix C: Unspecified Behavior 481Bibliography 487Index 495