BADFUNC.CHROOT : Use of chroot

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 chroot(), which requires that certain precautions be taken.

This class is a strict superset of chroot without chdir.

Class Name

Use of chroot

Significance

security

Mnemonic

BADFUNC.CHROOT

Categories

CWE	CWE:242	Use of Inherently Dangerous Function
	CWE:243	Creation of chroot Jail Without Changing Working Directory
	CWE:676	Use of Potentially Dangerous Function
CERT-C	CERT-C:POS05-C	Limit access to files by creating a jail
BSI	BSI:CHROOT-01
	BSI:CHROOT-02
	BSI:CHROOT-03

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 chroot"

To enable all BSI-related classes, including all BSI-specific BADFUNC classes, use the bsi configuration preset.

CWE:272	Least Privilege Violation

CWE:272

Least Privilege Violation

When you are warned about a use of chroot(), check that the following conditions are satisfied.

All open file descriptors are closed before any chroot() call, or as soon as possible afterward.

There is a chdir("/") call as soon as possible after any chroot() call.

The user ID and group ID of the process are changed to something more restrictive as soon as possible after any chroot() call.

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.CHROOT : Use of chroot

Summary

Properties

Could Also Indicate

Resolution

Relevant Configuration File Parameters