CERT Secure Coding

Space shortcuts

Space Tools

An 'undefined' page is any page that has been linked to from within Confluence, but that does not yet exist.

  1. Prev
  2. 1
  3. 2
  4. Next
Undefined Page Linked From
... Comment: INT01-C. Use rsize_t or size_t for all integer values representing the size of an object > Re: INT01-C. Use rsize_t or size_t for all integer values representing the size of an object (SEI CERT C Coding Standard)
0 Comment: ENV03-C. Sanitize the environment when invoking external programs > Re: ENV03-C. Sanitize the environment when invoking external programs (SEI CERT C Coding Standard)
Comment: MEM33-C. Allocate and copy structures containing a flexible array member dynamically > Re: MEM33-C. Allocate and copy structures containing a flexible array member dynamically (SEI CERT C Coding Standard)
Comment: EXP08-C. Ensure pointer arithmetic is used correctly > Re: EXP08-C. Ensure pointer arithmetic is used correctly (SEI CERT C Coding Standard)
Comment: ENV03-C. Sanitize the environment when invoking external programs > Re: ENV03-C. Sanitize the environment when invoking external programs (SEI CERT C Coding Standard)
1 Comment: MEM33-C. Allocate and copy structures containing a flexible array member dynamically > Re: MEM33-C. Allocate and copy structures containing a flexible array member dynamically (SEI CERT C Coding Standard)
10 Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard)
1234 Comment: EXP09-C. Use sizeof to determine the size of a type or variable > Re: EXP09-C. Use sizeof to determine the size of a type or variable (SEI CERT C Coding Standard)
12345678 Comment: EXP09-C. Use sizeof to determine the size of a type or variable > Re: EXP09-C. Use sizeof to determine the size of a type or variable (SEI CERT C Coding Standard)
3 Comment: DCL03-C. Use a static assertion to test the value of a constant expression > Re: DCL03-C. Use a static assertion to test the value of a constant expression (SEI CERT C Coding Standard)
4 Comment: DCL03-C. Use a static assertion to test the value of a constant expression > Re: DCL03-C. Use a static assertion to test the value of a constant expression (SEI CERT C Coding Standard)
API05-C. Support compile-time checking Comment: Rule 13. Application Programming Interfaces (API) > Re: Rule 13. Application Programming Interfaces (API) (SEI CERT C Coding Standard)
API06-C. Make failures obvious Comment: Rule 13. Application Programming Interfaces (API) > Re: Rule 13. Application Programming Interfaces (API) (SEI CERT C Coding Standard)
CA-1995-14 Comment: ENV03-C. Sanitize the environment when invoking external programs > Re: ENV03-C. Sanitize the environment when invoking external programs (SEI CERT C Coding Standard)
CON32-C. When data must be accessed by multiple threads, provide a mutex and guarantee no adjacent data is also accessed Comment: CON34-C. Declare objects shared between threads with appropriate storage durations > Re: CON34-C. Declare objects shared between threads with appropriate storage durations (SEI CERT C Coding Standard)
Comment: POS38-C. Beware of race conditions when using fork and file descriptors > Re: POS38-C. Beware of race conditions when using fork and file descriptors (SEI CERT C Coding Standard)
DCL32-C. Guarantee that mutually visible identifiers are unique) Comment: DCL02-C. Use visually distinct identifiers > Re: DCL02-C. Use visually distinct identifiers (SEI CERT C Coding Standard)
DCL34-C. Use volatile for data that cannot be cached Comment: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction > Re: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction (SEI CERT C Coding Standard)
Comment: CON43-C. Do not allow data races in multithreaded code > Re: CON43-C. Do not allow data races in multithreaded code (SEI CERT C Coding Standard)
DCL39-C. Avoid information leak in structure padding Comment: EXP42-C. Do not compare padding data > Re: EXP42-C. Do not compare padding data (SEI CERT C Coding Standard)
ERR31-C. Don't redefine errno Comment: DCL37-C. Do not declare or define a reserved identifier > Re: DCL37-C. Do not declare or define a reserved identifier (SEI CERT C Coding Standard)
EXP30-C. Do not depend on order of evaluation between sequence points Comment: EXP35-C. Do not modify objects with temporary lifetime > Re: EXP35-C. Do not modify objects with temporary lifetime (SEI CERT C Coding Standard)
EXP31-C. Avoid side effects in assertions Comment: PRE31-C. Avoid side effects in arguments to unsafe macros > Re: PRE31-C. Avoid side effects in arguments to unsafe macros (SEI CERT C Coding Standard)
EXP32-C. Do not access a volatile object through a non-volatile reference Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard)
EXP33-C. Do not reference uninitialized memory Comment: DCL31-C. Declare identifiers before using them > Re: DCL31-C. Declare identifiers before using them (SEI CERT C Coding Standard)
EXP37-C. Call functions with the arguments intended by the API Comment: DCL05-C. Use typedefs of non-pointer types only > Re: DCL05-C. Use typedefs of non-pointer types only (SEI CERT C Coding Standard)
EXP40-C. Do not modify constant values Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard)
Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard)
Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard)
Comment: EXP32-C. Do not access a volatile object through a nonvolatile reference > Re: EXP32-C. Do not access a volatile object through a nonvolatile reference (SEI CERT C Coding Standard)
FIO18-CPP. Never expect write() to terminate the writing process at a null character Comment: FIO18-C. Never expect fwrite() to terminate the writing process at a null character > Re: FIO18-C. Never expect fwrite() to terminate the writing process at a null character (SEI CERT C Coding Standard)
FIO31-C. Do not open a file that is already open Comment: POS38-C. Beware of race conditions when using fork and file descriptors > Re: POS38-C. Beware of race conditions when using fork and file descriptors (SEI CERT C Coding Standard)
FIO43-C. Do not create temporary files in shared directories Comment: MSC24-C. Do not use deprecated or obsolescent functions > Re: MSC24-C. Do not use deprecated or obsolescent functions (SEI CERT C Coding Standard)
FLP03-C. Detect and handle floating point errors Comment: DCL00-C. Const-qualify immutable objects > Re: DCL00-C. Const-qualify immutable objects (SEI CERT C Coding Standard)
FLP33-C. Convert integers to floating point for floating point operations Comment: FLP30-C. Do not use floating-point variables as loop counters > Re: FLP30-C. Do not use floating-point variables as loop counters (SEI CERT C Coding Standard)
INT35-C. Evaluate integer expressions in a larger size before comparing or assigning to that size Comment: INT30-C. Ensure that unsigned integer operations do not wrap > Re: INT30-C. Ensure that unsigned integer operations do not wrap (SEI CERT C Coding Standard)
INT36-C. Do not perform bitwise and arithmetic operations on the same variable Comment: INT14-C. Avoid performing bitwise and arithmetic operations on the same data > Re: INT14-C. Avoid performing bitwise and arithmetic operations on the same data (SEI CERT C Coding Standard)
INT_MIN, INT_MAX Comment: INT01-C. Use rsize_t or size_t for all integer values representing the size of an object > Re: INT01-C. Use rsize_t or size_t for all integer values representing the size of an object (SEI CERT C Coding Standard)
  1. Prev
  2. 1
  3. 2
  4. Next