CWEweakness
CWE-243 Creation of chroot Jail Without Changing Working Directory
High
Official page ↗
- Abstraction
- Variant
- Structure
- Simple
- Status
- Draft
- Likelihood of exploit
- High
- Languages
- C, C++
- CWE version
- 5.0
Description
The product uses the chroot() system call to create a jail, but it does not change the working directory afterward.
Common consequences
• Confidentiality, Integrity: Read Files or Directories, Modify Files or Directories — If the working directory is not changed after the chroot() call, relative paths may still refer to file system resources outside of the jail. Attackers may be able to read or write to files outside of the jail.
Detection methods
• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)