Base weakness
Log in
Also known as: Stale file descriptor
The product uses or accesses a file descriptor after it has been closed.
Last updated
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.
1 recorded CVEs are caused by CWE-910 (Use of Expired File Descriptor). The highest-severity and most recent are shown first.
What can happen when CWE-910 is exploited.
Read Files or Directories
Affects: Confidentiality
The program could read data from the wrong file.
DoS: Crash, Exit, or Restart
Affects: Availability
Accessing a file descriptor that has been closed can cause a crash.
Typically introduced during these phases of the software lifecycle.
Languages
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.)
Effectiveness: High
Common questions about CWE-910.
The product uses or accesses a file descriptor after it has been closed.
1 recorded CVEs are attributed to CWE-910, including CVE-2020-13530.
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.)
Exploiting CWE-910 can lead to: Read Files or Directories, DoS: Crash, Exit, or Restart.
1 recorded CVEs are caused by CWE-910; none are currently in CISA's KEV catalog of actively exploited flaws.
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Get alerted the moment a new CWE-910 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.