Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated references from C11->C23

The formatted output functions (fprintf() and related functions) convert, format, and print their arguments under control of a format string, defined as follows by the . The C Standard, 7.2123.6.1, paragraph 3 [ISO/IEC 9899:20112024]:, specifies

The format shall be a multibyte character sequence, beginning and ending in its initial shift state. The format is composed of zero or more directives: ordinary multibyte characters (not %), which are copied unchanged to the output stream; and conversion specifications, each of which results in fetching zero or more subsequent arguments, converting them, if applicable, according to the corresponding conversion specifier, and then writing the result to the output stream.

...

  • Zero or more flags (in any order), which modify the meaning of the conversion specification
  • An optional minimum field width
  • An optional precision that gives the minimum number of digits, the maximum number of digits to appear for certain conversion specifiers, or the maximum number of bytes, etc. depending on the conversion specifier
  • An optional length modifier that specifies the size of the argument
  • A conversion specifier character that indicates the type of conversion to be applied

Common mistakes in creating format strings include

  • Providing insufficient an incorrect number of arguments for the format string
  • Using invalid conversion specifiers
  • Using a flag character that is incompatible with the conversion specifier
  • Using a length modifier that is incompatible with the conversion specifier
  • Mismatching the argument type and conversion specifier
  • Using an argument of type other than int for width or precision

The following table summarizes the compliance of various conversion specifications.   The first column contains a one or more conversion specifier character (or characters).   The next four columns consider the combination of the specifier character(s) characters with the various flags (the apostrophe ['], -, +, the space character, #, and # 0).   The next eight columns consider the combination of the specifier character(s) characters with the various length modifiers (h, hh, l, ll, j, z, t, and L).  Here, valid

Valid combinations are marked with a type name; arguments matched with the conversion specification will be are interpreted as that type.   For example, an argument matched with the specifier %hd will be is interpreted as a short, so short appears in the cell where d and h intersect.   The last column denotes the expected type types of arguments matched with the original specifier characters.

Valid character(s).  Throughout the table, valid and meaningful combinations are marked by the (tick) symbol (save for the length modifier columns, as described abovepreviously).   Valid combinations that have no effect are labeled N/E.   Using a combination marked by the (error) symbol, using a specification not represented in the table, or using an argument of an unexpected type may result in is undefined behavior. (See undefined behaviors 153, 155, 157, 158, 161, and 162 in Annex J of the C Standard.) 

Conversion
Specifier
Character

' XSI

-
+
SPACE


#


0

 


h


hh


l


ll


j


z


t


L

Argument
Type

d, i

(tick)

(tick)

(error)

(tick)

 

short

signed char

long

long long

intmax_t

size_t

ptrdiff_t

(error)

Signed integer

o

(error)

(tick)

(tick)

(tick)

 

unsigned short

unsigned char

unsigned long

unsigned long long

uintmax_t

size_t

ptrdiff_t

(error)

Unsigned integer

u

(tick)

(tick)

(error)

(tick)

 

unsigned short

unsigned  char

unsigned long

unsigned long long

uintmax_t

size_t

ptrdiff_t

(error)

Unsigned integer

x, X

(error)

(tick)

(tick)

(tick)

 

unsigned short

unsigned char

unsigned long

unsigned long long

uintmax_t

size_t

ptrdiff_t

(error)

Unsigned integer

f, F

(tick)

(tick)

(tick)

(tick)

 

(error)

(error)

N/E

N/E

(error)

(error)

(error)

long double

double or long double

e, E

(error)

(tick)

(tick)

(tick)

 

(error)

(error)

N/E

N/E

(error)

(error)

(error)

long double

double or long double

g, G

(tick)

(tick)

(tick)

(tick)

 

(error)

(error)

N/E

N/E

(error)

(error)

(error)

long double

double or long double

a, A

(tick)

(tick)

(tick)

(tick)

 

(error)

(error)

N/E

N/E

(error)

(error)

(error)

long double

double or long double

c

(error)

(tick)

(error)

(error)

 

(error)

(error)

wint_t

(error)

(error)

(error)

(error)

(error)

int or wint_t

s

(error)

(tick)

(error)

(error)

 

(error)

(error)

NTWS

(error)

(error)

(error)

(error)

(error)

NTBS or NTWS

p

(error)

(tick)

(error)

(error)

 

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

void*

n

(error)

(tick)

(error)

(error)

(error)

 

short*

char*

long*

long long*

intmax_t*

size_t*

ptrdiff_t*

(error)

Pointer to integer

C XSI

(error)

(tick)

(error)

(error)

 

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

wint_t

S XSI

(error)

(tick)

(error)

(error)

 

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

NTWS

%

(error)

(tick)

(error)

(error)

(error)

 

(error)

(error)

(error)

(error)

(error)

(error)

(error)

(error)

None

Legend     SPACE:

...

The space (" ") character
     N/E

...

: No effect

...

     NTBS: char* argument pointing to a null-terminated

...

character string

...

     NTWS: wchar_t* argument pointing to a null-terminated wide character string

...

     XSI: ISO/IEC 9945-2003 XSI extension

The format formatted input functions (fscanf() and related functions) use similarly - specified format strings and impose similar restrictions on their format strings and arguments.

Do not supply an unknown or invalid conversion specification or an invalid combination of flag character, precision, length modifier, or conversion specifier ; to a formatted IO function. Likewise, do not provide a number or type of arguments argument that do does not match the argument type of the conversion specifiers specifier used in the format string.

Format strings are usually string literals specified at the call site, but they need not be. They should, however, not contain unsanitized data; see However, they should not contain tainted values. (See FIO30-C. Exclude user input from format strings for more information.)

Noncompliant Code Example

Mismatches between arguments and conversion specifications may result in undefined behavior.   Many compilers can Compilers may diagnose type mismatches in formatted output function invocations.   In the following this noncompliant code example, the error_type argument to printf() is incorrectly matched with the %s s specifier , rather than with the %d specifierthe d specifier. Likewise, the the error_msg argument is incorrectly matched with the %d d specifier instead of the %sthe s specifier.   These usages result in undefined behavior. One possible result of this invocation is that printf() will interpret the error_type argument as a pointer , and try to read a string from the address that error_type contains. This is likely to result , possibly resulting in an access violation.

Code Block
bgColor#ffcccc
langc
#include <stdio.h>
 
void func(void) {
  const char *error_msg = "Resource not available to user.";
  int error_type = 3;
  /* ... */
  printf("Error (type %s): %d\n", error_type, error_msg);
  /* ... */
}

...

This compliant solution ensures that the format arguments to the printf() function match their respective format conversion specifications:

Code Block
bgColor#ccccff
langc
#include <stdio.h>
 
void func(void) {
  const char *error_msg = "Resource not available to user.";
  int error_type = 3;
  /* ... */
  printf("Error (type %d): %s\n", error_type, error_msg);

  /* ... */
}

Risk Assessment

In most cases, incorrectly Incorrectly specified format strings will can result in memory corruption or abnormal program termination. However, in some cases they can be used to corrupt memory in manners controllable by an attacker.

Rule

Recommendation

Severity

Likelihood

Remediation Cost

Priority

Level

FIO47-C

High

Unlikely

Medium

P6

L2

Automated Detection

Tool

Version

Checker

Description

Axivion Bauhaus Suite

Include Page
Axivion Bauhaus Suite_V
Axivion Bauhaus Suite_V

CertC-FIO47Fully implemented
CodeSonar
Include Page
CodeSonar_V
CodeSonar_V

IO.INJ.FMT
MISC.FMT
MISC.FMTTYPE

Format string injection
Format string
Format string type error

Coverity
Include Page
Coverity_V
Coverity_V
PWReports when the number of arguments differs from the number of required arguments according to the format string
GCC
Include Page
GCC_V
GCC_V

 


Can detect violations of this recommendation when the -Wformat flag is used

Helix QAC

Include Page
Helix QAC_V
Helix QAC_V

C0161, C0162, C0163, C0164, C0165, C0166, C0167, C0168, C0169, C0170, C0171, C0172, C0173, C0174, C0175, C0176, C0177, C0178, C0179, C0180, C0184, C0185, C0190, C0191, C0192, C0193, C0194, C0195, C0196, C0197, C0198, C0199, C0200, C0201, C0202, C0204, C0206, C0209

C++3150, C++3151, C++3152, C++3153, C++3154, C++3155, C++3156, C++3157, C++3158, C++3159


Klocwork
Include Page
Klocwork_V
Klocwork_V

SV.FMT_STR.PRINT_FORMAT_MISMATCH.BAD
SV.FMT_STR.PRINT_FORMAT_MISMATCH.UNDESIRED
SV.FMT_STR.PRINT_IMPROP_LENGTH
SV.FMT_STR.PRINT_PARAMS_WRONGNUM.FEW
SV.FMT_STR

 

.PRINT_PARAMS_WRONGNUM.MANY
SV.FMT_STR.SCAN_FORMAT_MISMATCH.BAD
SV.FMT_STR.SCAN_FORMAT_MISMATCH.UNDESIRED
SV.FMT_STR.SCAN_IMPROP_LENGTH
SV.FMT_STR.SCAN_PARAMS_WRONGNUM.FEW
SV.FMT_STR.SCAN_PARAMS_WRONGNUM.MANY
SV.FMT_STR.UNKWN_FORMAT


LDRA tool suite
Include Page
LDRA_V
LDRA_V

486 S
589 S

Fully implemented

PRQA QA-C Include PagePRQA_VPRQA_V

0179 (U)
0180 (C99)
0184 (U)
0185 (U)
0190 (U)
0191 (U)
0192 (U)
0193 (U)
0194 (U)
0195 (U)
0196 (U)
0197 (U)
0198 (U)
0199 (U)
0200 (U)
0201 (U)
0202 (I)
0206 (U)

Parasoft C/C++test
Include Page
Parasoft_V
Parasoft_V

CERT_C-FIO47-a
CERT_C-FIO47-b
CERT_C-FIO47-c
CERT_C-FIO47-d
CERT_C-FIO47-e
CERT_C-FIO47-f

There should be no mismatch between the '%s' and '%c' format specifiers in the format string and their corresponding arguments in the invocation of a string formatting function
There should be no mismatch between the '%f' format specifier in the format string and its corresponding argument in the invocation of a string formatting function
There should be no mismatch between the '%i' and '%d' format specifiers in the string and their corresponding arguments in the invocation of a string formatting function
There should be no mismatch between the '%u' format specifier in the format string and its corresponding argument in the invocation of a string formatting function
There should be no mismatch between the '%p' format specifier in the format string and its corresponding argument in the invocation of a string formatting function
The number of format specifiers in the format string and the number of corresponding arguments in the invocation of a string formatting function should be equal

PC-lint Plus

Include Page
PC-lint Plus_V
PC-lint Plus_V

492, 493, 494, 499, 557,
558, 559, 566, 705, 706,
719, 816, 855, 2401, 2402,
2403, 2404, 2405, 2406, 2407

Fully supported

Polyspace Bug Finder

Include Page
Polyspace Bug Finder_V
Polyspace Bug Finder_V

CERT C: Rule FIO47-C

Check for format string specifiers and arguments mismatch (rule fully covered)

PVS-Studio

Include Page
PVS-Studio_V
PVS-Studio_V

V510, V576
TrustInSoft Analyzer

Include Page
TrustInSoft Analyzer_V
TrustInSoft Analyzer_V

match format and argumentsExhaustively verified (see the compliant and the non-compliant example).
Partially implemented

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Related Guidelines

Key here (explains table format and definitions)

Taxonomy

Taxonomy item

Relationship

CERT C
++ Secure Coding Standard
FIO00-CPP. Take care when creating format stringsPrior to 2018-01-12: CERT: Unspecified Relationship
ISO/IEC TS 17961:2013Using invalid format strings [invfmtstr]
MITRE CWE
Prior to 2018-01-12: CERT: Unspecified Relationship
CWE 2.11CWE-686, Function
call with incorrect argument type
Call with Incorrect Argument Type2017-06-29: CERT: Partial overlap
CWE 2.11CWE-6852017-06-29: CERT: Partial overlap

CERT-CWE Mapping Notes

Key here for mapping notes

CWE-686 and FIO47-C

Intersection( EXP37-C, FIO47-C) =


  • Invalid argument types passed to format I/O function


EXP37-C – FIO47-C =


  • Invalid argument types passed to non-format I/O function


FIO47-C – EXP37-C =


  • Invalid format string, but correctly matches arguments in number and type


Intersection( CWE-686, FIO47-C) =


  • Use of format strings that do not match the type of arguments


CWE-686 – FIO47-C =


  • Incorrect argument type in functions outside of the printf() family.


FIO47-C – CWE-686 =


  • Invalid format strings that still match their arguments in type


CWE-685 and FIO47-C

Intersection( CWE-685, FIO47-C) =


  • Use of format strings that do not match the number of arguments


CWE-685 – FIO47-C =


  • Incorrect argument number in functions outside of the printf() family.


FIO47-C – CWE-685 =


  • Invalid format strings that still match their arguments in number


CWE-134 and FIO47-C

Intersection( FIO30-C, FIO47-C) =


  • Use of untrusted and ill-specified format string


FIO30-C – FIO47-C =


  • Use of untrusted, but well-defined format string


FIO47-C – FIO30-C =


  • Use of Ill-defined, but trusted format string


FIO47-C = Union(CWE-134, list) where list =


  • Using a trusted but invalid format string


Bibliography

[ISO/IEC 9899:
2011
2024]Subclause 7.
21
23.6.1, "The fprintf Function"

...


...

Image Modified Image Modified Image Modified