C and C++ Binaries


BADFUNC.BO.GETPASS : Use of getpass

Summary

A use of getpass(), which may be vulnerable to internal buffer overflows depending on the implementation.

Properties

Class Name Use of getpass
Significance security
Mnemonic BADFUNC.BO.GETPASS
Categories
AUTOSARC++14 AUTOSARC++14:A5-2-5 An array or container shall not be accessed beyond its range.
CWE CWE:120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
  CWE:676 Use of Potentially Dangerous Function
CERT-CPP CERT-CPP:CTR52-CPP Guarantee that library functions do not overflow
DISA-6r1 DISA-6r1:V-222612 The application must not be vulnerable to overflow attacks.
DISA-5r3 DISA-5r3:V-70277 The application must not be vulnerable to overflow attacks.
DISA-4r3 DISA-4r3:V-70277 The application must not be vulnerable to overflow attacks.
DISA-3r10 DISA-3r10:V-6165 The designer will ensure the application does not have buffer overflows, use functions known to be vulnerable to buffer overflows, and does not use signed values for memory allocation where permitted by the programming language.
BSI BSI:GETPASS Use of getpass
Availability Available for C and C++.
Enabling Checks for this warning class are disabled by default. To enable them, add the following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += allow class="Use of getpass"
To enable all BSI-related classes, including all BSI-specific BADFUNC classes, use the bsi configuration preset.

Resolution

Is the implementation of getpass() you are using prone to internal buffer overflows?

if YES: Read the bug reports and security notices for getpass() on your platform to determine what approaches are recommended.
  • When you see a Use of getpass warning, make sure that the recommended checks are carried out. If so, you can change the warning state to Suppressed.
  • Alternatively, use readpassphrase() instead of getpass().
  • Alternatively, upgrade your library to a version that does not have these vulnerabilities.
if NO: there is no need to enable this warning class.

Relevant Configuration File Parameters

This class is implemented using a BAD_FUNCTION_* rule set in the general template configuration file.

The following configuration file parameters affect checks for this warning class.