- What is CWE-774?
- The product allocates file descriptors or handles on behalf of an actor without imposing any restrictions on how many descriptors can be allocated, in violation of the intended security policy for that actor.
- What CVEs are caused by CWE-774?
- 1 recorded CVEs are attributed to CWE-774, including CVE-2024-48848.
- How do you prevent CWE-774?
- Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
- How is CWE-774 detected?
- 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.)
- What are the consequences of CWE-774?
- Exploiting CWE-774 can lead to: DoS: Resource Consumption (Other).
- Is CWE-774 actively exploited?
- 1 recorded CVEs are caused by CWE-774; none are currently in CISA's KEV catalog of actively exploited flaws.
