Détail du CWE-403

A process does not close sensitive file descriptors before invoking a child process, which allows the child to perform unauthorized I/O operations using those descriptors.

When a new process is forked or executed, the child process inherits any open file descriptors. When the child process has fewer privileges than the parent process, this might introduce a vulnerability if the child process can access the file descriptor but does not have the privileges to access the associated file.

Modes d'introduction

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

Plateformes applicables

Langue

Name: C (Undetermined)
Class: Not Language-Specific (Undetermined)

Systèmes d’exploitation

Class: Unix (Undetermined)

Conséquences courantes

Exemples observés

Notes de cartographie des vulnérabilités

Justification : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Commentaire : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Références

REF-392

File descriptors and setuid applications
Paul Roberts.
https://blogs.oracle.com/paulr/entry/file_descriptors_and_setuid_applications

REF-393

Introduction to Secure Coding Guide
Apple.
https://developer.apple.com/library/archive/documentation/Security/Conceptual/SecureCodingGuide/Articles/AccessControl.html

Soumission

Modifications