Scanf Explained

scanf, short for scan formatted, is a C standard library function that reads and parses text from standard input.

The function accepts a format string parameter that specifies the layout of input text. The function parses input text and loads values into variables based on data type.

Similar functions, with other names, predate C, such as readf in ALGOL 68.

Input format strings are complementary to output format strings (see printf), which provide formatted output (templating).

History

Mike Lesk's portable input/output library, including scanf, officially became part of Unix in Version 7.[1]

Usage

The scanf function reads input for numbers and other datatypes from standard input.

The following C code reads a variable number of unformatted decimal integers from standard input and prints each of them out on separate lines:

  1. include

int main(void)

For input:

456 123 789 456 12 456 1 2378

The output is:4561237894561245612378

To print out a word:

  1. include

int main(void)

No matter what the data type the programmer wants the program to read, the arguments (such as &n above) must be pointers pointing to memory. Otherwise, the function will not perform correctly because it will be attempting to overwrite the wrong sections of memory, rather than pointing to the memory location of the variable you are attempting to get input for.

In the last example an address-of operator (&) is not used for the argument: as word is the name of an array of char, as such it is (in all contexts in which it evaluates to an address) equivalent to a pointer to the first element of the array. While the expression &word would numerically evaluate to the same value, semantically, it has an entirely different meaning in that it stands for the address of the whole array rather than an element of it. This fact needs to be kept in mind when assigning scanf output to strings.

As scanf is designated to read only from standard input, many programming languages with interfaces, such as PHP, have derivatives such as sscanf and fscanf but not scanf itself.

Format string specifications

The formatting placeholders in scanf are more or less the same as that in printf, its reverse function. As in printf, the POSIX extension is defined.

There are rarely constants (i.e., characters that are not formatting placeholders) in a format string, mainly because a program is usually not designed to read known data, although scanf does accept these if explicitly specified. The exception is one or more whitespace characters, which discards all whitespace characters in the input.

Some of the most commonly used placeholders follow:

The above can be used in compound with numeric modifiers and the l, L modifiers which stand for "long" and "long long" in between the percent symbol and the letter. There can also be numeric values between the percent symbol and the letters, preceding the long modifiers if any, that specifies the number of characters to be scanned. An optional asterisk (*) right after the percent symbol denotes that the datum read by this format specifier is not to be stored in a variable. No argument behind the format string should be included for this dropped variable.

The ff modifier in printf is not present in scanf, causing differences between modes of input and output. The ll and hh modifiers are not present in the C90 standard, but are present in the C99 standard.[2]

An example of a format string is

"%7d%s %c%lf"The above format string scans the first seven characters as a decimal integer, then reads the remaining as a string until a space, newline, or tab is found, then consumes whitespace until the first non-whitespace character is found, then consumes that character, and finally scans the remaining characters as a double. Therefore, a robust program must check whether the scanf call succeeded and take appropriate action. If the input was not in the correct format, the erroneous data will still be on the input stream and must discarded before new input can be read. An alternative method, which avoids this, is to use [[fgets]] and then examine the string read in. The last step can be done by [[sscanf]], for example.

In the case of the many float type characters, many implementations choose to collapse most into the same parser. Microsoft MSVCRT does it with,[3] while glibc does so with all four.

ISO C99 includes the [[inttypes.h]] header file that includes a number of macros for use in platform-independent coding. These must be outside double-quotes, e.g.

Example macros include:

MacroDescription
Typically equivalent to (Win32/Win64) or
Typically equivalent to (Win32/Win64), (32-bit platforms) or (64-bit platforms)
Typically equivalent to (Win32/Win64) or
Typically equivalent to (Win32/Win64), (32-bit platforms) or (64-bit platforms)
Typically equivalent to (Win32/Win64) or
Typically equivalent to (Win32/Win64), (32-bit platforms) or (64-bit platforms)
Typically equivalent to (Win32/Win64) or
Typically equivalent to (Win32/Win64), (32-bit platforms) or (64-bit platforms)

Vulnerabilities

scanf is vulnerable to format string attacks. Great care should be taken to ensure that the formatting string includes limitations for string and array sizes. In most cases the input string size from a user is arbitrary and cannot be determined before the scanf function is executed. This means that %s placeholders without length specifiers are inherently insecure and exploitable for buffer overflows. Another potential problem is to allow dynamic formatting strings, for example formatting strings stored in configuration files or other user-controlled files. In this case the allowed input length of string sizes cannot be specified unless the formatting string is checked beforehand and limitations are enforced. Related to this are additional or mismatched formatting placeholders which do not match the actual vararg list. These placeholders might be partially extracted from the stack or contain undesirable or even insecure pointers, depending on the particular implementation of varargs.

See also

External links

Notes and References

  1. M. D. . McIlroy . Doug McIlroy . 1987 . A Research Unix reader: annotated excerpts from the Programmer's Manual, 1971–1986 . CSTR . 139 . Bell Labs.
  2. C99 standard, §7.19.6.2 "The fscanf function" alinea 11.
  3. Web site: scanf Type Field Characters . docs.microsoft.com . 26 October 2022 .