BADFUNC.TEMP.TMPNAM : Use of tmpnam

JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

A use of tmpnam(), tmpnam_r(), _tmpnam(), _ttmpnam(), _wtmpnam(), tempnam(), _ttempnam(), _wtempnam(), or GetTempFileName(), which are associated with temporary file vulnerabilities.

Class Name

Use of tmpnam

Significance

security

Mnemonic

BADFUNC.TEMP.TMPNAM

Categories

CWE	CWE:242	Use of Inherently Dangerous Function
	CWE:377	Insecure Temporary File
	CWE:676	Use of Potentially Dangerous Function
CERT-C	CERT-C:CON33-C	Avoid race conditions when using library functions
	CERT-C:FIO01-C	Be careful using functions that use file names for identification
	CERT-C:FIO21-C	Do not create temporary files in shared directories
OWASP-2017	OWASP-2017:A9	Using components with known vulnerabilities
OWASP-2021	OWASP-2021:A6	Vulnerable and outdated components

Availability

Available for C and C++.

Enabling

Checks for this warning class are enabled by default. To disable them, add the following WARNING_FILTER rule to the project configuration file.

WARNING_FILTER += discard class="Use of tmpnam"

When you see a Use of tmpnam warning, make sure that security risks have been minimized as much as possible.

Create temporary files in a secure directory, with appropriate umask and mode, and with names that cannot be easily guessed.

Delete temporary files as soon as they are no longer needed.

Avoid interleaved operations on temporary files as much as possible.

If so, you can change the warning state to Suppressed.

To include an additional function or set of functions in the checks for this class, create a new set of BAD_FUNCTION_* rules in which the BAD_FUNCTION_REGEX setting matches the function or set of functions you want to check and the remaining rules match those in the other sets for this class.

To remove a function or set of functions from the checks for this class, edit the configuration file to comment out the corresponding set of BAD_FUNCTION_* rules.

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

BADFUNC.TEMP.TMPNAM : Use of tmpnam

Summary

Properties

Resolution

Relevant Configuration File Parameters