The product's resource pool is not large enough to handle peak demand, which allows an attacker to prevent others from accessing the resource by using a (relatively) large number of requests for resources.
View on MITREFrequently the consequence is a "flood" of connection or sessions.
No consequence information available for this CWE.
Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests.
Consider implementing a velocity check mechanism which would detect abusive behavior.
Consider load balancing as an option to handle heavy loads.
Make sure that resource handles are properly closed when no longer needed.
Identify the system's resource intensive operations and consider protecting them from abuse (e.g. malicious automated script which runs the resources out).
No detection method information available for this CWE.
In the following snippet from a Tomcat configuration file, a JDBC connection pool is defined with a maximum of 5 simultaneous connections (with a 60 second timeout). In this case, it may be trivial for an attacker to instigate a denial of service (DoS) by using up all of the available connections in the pool.
Product supports only one connection and does not disconnect a user who does not provide credentials.
View DetailsLarge number of connections without providing credentials allows connection exhaustion.
View DetailsNo relationship information available for this CWE.
CWE-410: Insufficient Resource Pool is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product's resource pool is not large enough to handle peak demand, which allows an attacker to prevent others from accessing the resource by using a (relatively) large number of requests for resources. Frequently the consequence is a "flood" of connection or sessions.
Recommended mitigations for CWE-410 include: Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests. Consider implementing a velocity check mechanism which would detect abusive behavior. Consider load balancing as an option to handle heavy loads.
CWE-410 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
MITRE documents real CVEs mapped to CWE-410, including CVE-1999-1363, CVE-2001-1340 and CVE-2002-0406. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
A CWE (Common Weakness Enumeration) like CWE-410 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.