The program calls a function that can never be guaranteed to work safely.
Certain functions behave in dangerous ways regardless of how they are used. Functions in this category were often implemented without taking security concerns into account. The gets() function is unsafe because it does not perform bounds checking on the size of its input. An attacker can easily send arbitrarily-sized input to gets() and overflow the destination buffer. Similarly, the >> operator is unsafe to use when reading into a statically-allocated character array because it does not perform bounds checking on the size of its input. An attacker can easily send arbitrarily-sized input to the >> operator and overflow the destination buffer.
Time of Introduction
Technical Impact: Varies by context
Likelihood of Exploit
The code below calls gets() to read information into a
The gets() function in C is inherently unsafe.
The code below calls the gets() function to read in data from the
printf("Please enter your name and press
However, the programmer uses the function gets() which is inherently
unsafe because it blindly copies all input from STDIN to the buffer
without checking size. This allows the user to provide a string that is
larger than the buffer size, resulting in an overflow condition.
Phases: Implementation; Requirements
Ban the use of dangerous functions. Use their safe equivalent.
Use grep or static analysis tools to spot usage of dangerous
the weakness exists independent of other weaknesses)