...
Tip |
---|
The table below can be re-ordered, by clicking column headers. |
...
Include Page | ||||
---|---|---|---|---|
|
FIO11
Take care when specifying the mode parameter of fopen() Bad STR38
Do not Guarantee that storage for strings has sufficient space for character data and null terminator
STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator memory
ARR38
Guarantee that library functions do not form invalid pointers
API00
Functions should validate their parameters
API00-C. Functions should validate their parameters Invalid use of standard library string routine
string
STR32
pass a non-null-terminated character sequence to a library function that expects a string
string
va_list argument MSC39
Do not call va_arg() on a va_list that has an indeterminate value Library loaded from externally controlled path STR02-C. Sanitize data passed to complex subsystems Library loaded from externally controlled path WIN00-C. Be specific when dynamically loading libraries Load of library from a relative path can be controlled by an external actor WIN00-C. Be specific when dynamically loading libraries Loop bounded with tainted value INT04-C. Enforce limits on integer values originating from tainted sources Loop bounded with tainted value MSC21-C. Use robust loop termination conditions Memory allocation with tainted size MEM35-C. Allocate sufficient memory for an object Memory allocation with tainted size INT04-C. Enforce limits on integer values originating from tainted sources Memory allocation with tainted size MEM07-C. Ensure that the arguments to calloc(), when multiplied, do not wrap Memory allocation with tainted size MEM10-C. Define and use a pointer validation function Memory allocation with tainted size MEM11-C. Do not assume infinite heap space Memory comparison of float-point values FLP37-C. Do not use object representations to compare floating-point values Memory comparison of padding data EXP42-C. Do not compare padding data Memory leak MEM31-C. Free dynamically allocated memory when no longer needed Memory leak
leak MEM12-C. Consider using a goto chain when leaving a function on error when using and releasing resources Mismatch between data length and size
MISRA2012-DIR-1_1 FLP30-
use floating-point variables as loop counters MISRA2012-RULE-8_1 DCL31-C. Declare identifiers before using them MISRA2012-RULE-8_2
DCL36
declare an identifier with conflicting linkage classifications MISRA2012-RULE-8_4 DCL36-C. Do not declare an identifier with conflicting linkage classifications MISRA2012-RULE-8_8
MISRA2012-RULE-13_
PRE31
Avoid side effects in arguments to unsafe macros
MISRA2012-RULE-13_2 EXP30
depend on the order of evaluation for side effects MISRA2012-RULE-14_1 FLP30-C. Do not use floating-point variables as loop counters MISRA2012-RULE-17_3 DCL31-C. Declare identifiers before using them MISRA2012-RULE-17_3
MISRA2012-RULE-21_1 DCL37-C. Do not declare or define a reserved identifier MISRA2012-RULE-21_2 DCL37-C. Do not declare or define a reserved identifier the same module, at the same level of abstraction array subscripts Returned create a universal character name through concatenation with a pointer to an automatic variable as the argument
EXP37-C. |
STR31-C. |
Function called from signal-handler not asynchronous safe | SIG30-C. Call only asynchronous-safe functions within signal handlers |
integer routine |
STR37-C. |
Arguments to character-handling functions must be representable as an unsigned char |
Invalid use of standard library memory routine |
EXP34-C. |
Do not dereference null pointers |
Invalid use of standard library memory routine |
ARR38-C. Guarantee that library functions do not form invalid pointers |
Invalid use of standard library |
memory routine |
ARR39-C. Do not |
add or subtract a scaled integer to a pointer | |
Invalid use of standard library memory routine | API00-C. Functions should validate their parameters |
Invalid use of standard library |
routine | API00-C. Functions should validate their parameters |
Invalid |
use of standard library string routine | ARR38-C. |
MEM11-C. Do not assume infinite heap space | |
Memory |
MISRA C:2012 Dir 4.13 | MEM30- |
C. Do not |
access freed memory | |
MISRA C:2012 Directive 4.5 | DCL02-C. Use visually distinct identifiers |
MISRA C:2012 Directive 4.14 | EXP34 |
-C. Do not |
DCL36-C. Do not declare an identifier with conflicting linkage classifications |
MISRA C:2012 Rule 8.2 |
DCL07-C. |
Include the appropriate type information in function declarators | |
MISRA C:2012 Rule 8.3 | DCL40 |
-C. Do not |
DCL36-C. Do not declare an identifier with conflicting linkage classifications |