...
Anchor analyzer analyzer
analyzer [ISO/IEC 9899TS 17961:20112013]
Mechanism that diagnoses coding flaws in software programs.
...
- Call the
signal()
function to reinstall a signal handler. - Unconditionally modify a
volatile sig_atomic_t
variable (as modification to this type is atomic). - Call the
_Exit()
function to immediately terminate program execution. - Invoke an asynchronous-safe function, as specified by the implementation.
Few functions are portably asynchronous-safe.
...
Anchor | ||||
---|---|---|---|---|
|
critical sections
Shared data that Code that accesses shared data and would otherwise be protected from data races.
...
NOTE
Tracking can be performed intraprocedurally, with various assumptions made about what happens at function call boundaries, or interprocedurally, where values are tracked flowing into function calls (directly or indirectly) as arguments and flowing back out either as return values or indirectly through arguments.
Data flow analysis may or may not track values flowing into or out of the heap or take into account global variables. When this specification refers to values flowing, the key point is contrast with variables or expressions , because a given variable or expression may hold different values along different paths , and a given value may be held by multiple variables or expressions along a path.
...
Anchor diagnostic message diagnostic message
diagnostic message [ISO/IEC 9899:2011]
A diagnostic message is a message A message belonging to an implementation-defined subset of the implementation’s message output. A diagnostic message may indicate a constraint violation or a valid but questionable language construct. Messages typically include the file name and line number pointing to the offending code construct. In addition, implementations also often indicate the severity of the problem. Although the C Standard does not specify any such requirement, the most severe problems often cause implementations to fail to fully translate a translation unit. Diagnostics output in such cases are termed errors. Other problems may cause implementations simply to issue a warning message and continue translating the rest of the program. See error message and warning message.
...
Anchor | ||||
---|---|---|---|---|
|
fatal diagnostic
A diagnostic message which that causes an implementation not to perform the translation.
...
Anchor | ||||
---|---|---|---|---|
|
in-band error indicator[ISO/IEC 9899TS 17961:20112013]
A library function return value on error that can never be returned by a successful call to that library function.
...
Anchor | ||||
---|---|---|---|---|
|
mitigation [Seacord 2005a]
Methods, techniques, processes, tools, or runtime libraries that can prevent or limit exploits against vulnerabilities.
Anchor | mutilated value | mutilated value |
---|
Result of an operation performed on an untainted value that yields either an undefined result (such as the result of signed integer overflow), the result of right-shifting a negative number, implicit conversion to an integral type where the value cannot be represented in the destination type, or unsigned integer wrapping.
EXAMPLEint j = INT_MAX + 1; // j is mutilated
char c = 1234; // c is mutilated if char is eight bits
unsigned int u = 0U - 1; // u is mutilated
NOTE
A mutilated value can be just as dangerous as a tainted value because it can differ either in sign or magnitude from what the programmer expects.
|
nonpersistent signal handler
Signal handler running on an implementation that requires
Signal handler running on an implementation that requires the program to again register the signal handler after occurrences of the signal to catch subsequent occurrences of that signal.
Anchor | ||||
---|---|---|---|---|
|
normal program termination [IEEE Std 1003.1-2013]
Normal termination occurs by a return from
main()
, when requested with the exit()
, _exit()
, or _Exit()
functions, or when the last thread in the process terminates by returning from its start function , by calling the pthread_exit()
function, or through cancellation. See abnormal termination....
NOTE
The IEC 60559 standard for binary floating-point arithmetic requires certain user-accessible status flags and control modes. Floating-point operations implicitly set the status flags; modes affect result values of floating-point operations. Implementations that support such floatinga floating-point state are required to regard changes to it as side effects. These are detailed in Annex F of the C Standard.
...
Anchor | ||||
---|---|---|---|---|
|
string [ISO/IEC 9899:2011]
A string is a contiguous sequence of characters terminated by and including the first null character.
...
- parameters to the
main()
function, - the returned values from
localeconv()
,fgetc()
,getc
,getchar
,()
fgetwc
,()
getwc
, and()
getwchar
()
, and - the strings produced by
getenv
,()
fscanf
,()
vfscanf
()
,vscanf
,()
fgets
()
,fread
,()
fwscanf
()
,vfwscanf
,()
vwscanf
,()
wscanf
, and()
fgetws
()
.
- parameters to the
Anchor | ||||
---|---|---|---|---|
|
tainted value [ISO/IEC TS 17961:2013]
Value derived from a tainted source that has not been sanitized.
...
NOTE
For the purposes of this definition, a pointer to an object that is not an element of an array behaves the same as a pointer to the first element of an array of length one with the type of the object as its element type. (see See C Standard, 6.5.8, paragraph 4.).
For the purposes of this definition, an object can be considered to be an array of a certain number of bytes; that number is the size of the object , as produced by the sizeof
operator. (see See C Standard, 6.3.2.3, paragraph 7.).
Anchor | ||||
---|---|---|---|---|
|
validation [IEC 61508-4]
Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled.
...