Use of Expired File Descriptor

The product uses or accesses a file descriptor after it has been closed.

Soyutlama

Base

Yapı

Simple

Sömürü İhtimali

Medium

Problemi anla

Problem nedir?

The product uses or accesses a file descriptor after it has been closed.

Genişletilmiş açıklama

After a file descriptor for a particular file or device has been released, it can be reused. The code might not write to the original file, since the reused file descriptor might reference a different file or device.

Terminoloji

Alternatif adlar ve kullanım biçimleri

Stale file descriptor

Kök neden

Problem nasıl ve ne zaman oluşur?

Yaşam döngüsü evresi

Implementation

Risk

Başarılı sömürü neye yol açar?

Read Files or Directories

Etkilenen güvenlik alanları: Confidentiality

The program could read data from the wrong file.

DoS: Crash, Exit, or Restart

Etkilenen güvenlik alanları: Availability

Accessing a file descriptor that has been closed can cause a crash.

Savunma

Nasıl önlenir ve çözülür?

Follow secure coding guidelines for input handling and boundary checking.
Enforce strict security reviews and automated static analysis (SAST) checks.

Doğrulama

Nasıl tespit edilir?

Automated Static Analysis

High

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.)