CWE

Common Weakness Enumeration

A Community-Developed List of Software Weakness Types

CWE/SANS Top 25 Most Dangerous Software Errors
Home > CWE List > CWE- Individual Dictionary Definition (2.10)  
ID

CWE-910: Use of Expired File Descriptor

Weakness ID: 910
Abstraction: Base
Status: Incomplete
Presentation Filter:
+ Description

Description Summary

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

Extended Description

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.

+ Alternate Terms
Stale file descriptor
+ Time of Introduction
  • Implementation
+ Applicable Platforms

Languages

C: (Sometimes)

C++: (Sometimes)

Language-independent

+ Common Consequences
ScopeEffect
Confidentiality

Technical Impact: Read files or directories

The program could read data from the wrong file.

Availability

Technical Impact: DoS: crash / exit / restart

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

+ Likelihood of Exploit

Medium

+ Weakness Ordinalities
OrdinalityDescription
Primary
(where the weakness exists independent of other weaknesses)
Resultant
(where the weakness is typically related to the presence of some other weaknesses)
+ Relationships
NatureTypeIDNameView(s) this relationship pertains toView(s)
ChildOfCategoryCategory452Initialization and Cleanup Errors
Development Concepts (primary)699
ChildOfWeakness BaseWeakness Base672Operation on a Resource after Expiration or Release
Research Concepts (primary)1000
+ Content History
Submissions
Submission DateSubmitterOrganizationSource
2012-12-21MITREInternal CWE Team
New weakness based on discussion on the CWE research list in December 2012.

More information is available — Please select a different filter.
Page Last Updated: January 18, 2017