Creation of chroot Jail Without Changing Working Directory

Opis

The product uses the chroot() system call to create a jail, but does not change the working directory afterward. This does not prevent access to files outside of the jail.

Improper use of chroot() may allow attackers to escape from the chroot jail. The chroot() function call does not change the process's current working directory, so relative paths may still refer to file system resources outside of the chroot jail after chroot() has been called.

Skutki

• Confidentiality

  Read Files or Directories

Słabość nadrzędna

• CWE-573 Improper Following of Specification by Caller
• CWE-669 Incorrect Resource Transfer Between Spheres

Kiedy powstaje

• Implementation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Dotyczy

C, C++, Unix

Źródła

1. Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors — Katrina Tsipenyuk, Brian Chess, Gary McGraw, NIST, 2005