Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.
CWE-410 Classe Incompleto
Insufficient Resource Pool
This vulnerability occurs when a system's resource pool is too small to handle maximum usage. Attackers can exploit this by making a high volume of requests, consuming all available resources and…
Definição
What is CWE-410?
This vulnerability occurs when a system's resource pool is too small to handle maximum usage. Attackers can exploit this by making a high volume of requests, consuming all available resources and blocking legitimate users.
At its core, this weakness creates a denial-of-service condition by exhausting a finite resource pool—like database connections, threads, or memory blocks. When an attacker floods the system with requests, the pool is quickly depleted, preventing normal users from accessing the service. This often manifests as connection timeouts, application crashes, or severe performance degradation during traffic spikes.
To prevent this, developers must design resource pools that scale under peak load and implement safeguards like rate limiting, request throttling, and automatic resource recycling. Monitoring usage patterns and setting up alerts for abnormal consumption are also critical, as they allow teams to respond before a full outage occurs.
Impacto no mundo real
Real-world CVEs caused by CWE-410
-
Large number of locks on file exhausts the pool and causes crash.
-
Product supports only one connection and does not disconnect a user who does not provide credentials.
-
Large number of connections without providing credentials allows connection exhaustion.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable XML
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.
<Resource name="jdbc/exampledb"
auth="Container"
type="javax.sql.DataSource"
removeAbandoned="true"
removeAbandonedTimeout="30"
maxActive="5"
maxIdle="5"
maxWait="60000"
username="testuser"
password="testpass"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost/exampledb"/> Exemplo de código seguro
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de verificação de prevenção
How to prevent CWE-410
- Architecture and Design Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests.
- Architecture and Design Consider implementing a velocity check mechanism which would detect abusive behavior.
- Operation Consider load balancing as an option to handle heavy loads.
- Implementation Make sure that resource handles are properly closed when no longer needed.
- Architecture and Design Identify the system's resource intensive operations and consider protecting them from abuse (e.g. malicious automated script which runs the resources out).
Sinais de deteção
How to detect CWE-410
Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.
Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.
Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.
CWE-410
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Perguntas frequentes O que é o CWE-410?
Qual a gravidade do CWE-410?
Que linguagens ou plataformas são afetadas pelo CWE-410?
Como posso prevenir o CWE-410?
Como é que o Plexicus deteta e corrige o CWE-410?
Onde posso saber mais sobre o CWE-410?
Frequently asked questions
O que é o CWE-410?
This vulnerability occurs when a system's resource pool is too small to handle maximum usage. Attackers can exploit this by making a high volume of requests, consuming all available resources and blocking legitimate users.
Qual a gravidade do CWE-410?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-410?
A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.
Como posso prevenir o CWE-410?
Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests. Consider implementing a velocity check mechanism which would detect abusive behavior.
Como é que o Plexicus deteta e corrige o CWE-410?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-410 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-410?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/410.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-410
CWE-664 Pai
Improper Control of a Resource Through its Lifetime
This vulnerability occurs when software fails to properly manage a resource throughout its entire lifecycle—from creation and active use…
CWE-118 Irmão
Incorrect Access of Indexable Resource ('Range Error')
This vulnerability occurs when software fails to properly check the boundaries of an indexed resource, like an array, buffer, or file,…
CWE-1229 Irmão
Creation of Emergent Resource
This vulnerability occurs when a system's normal operations unintentionally create new, exploitable resources that attackers can use to…
CWE-1250 Irmão
Improper Preservation of Consistency Between Independent Representations of Shared State
This vulnerability occurs when a system with multiple independent components (like distributed services or separate hardware units) each…
CWE-1329 Irmão
Reliance on Component That is Not Updateable
This vulnerability occurs when a product depends on a component that cannot be updated or patched to fix security flaws or critical bugs.
CWE-221 Irmão
Information Loss or Omission
This weakness occurs when an application fails to log critical security events or records them inaccurately, which can misguide security…
CWE-372 Irmão
Incomplete Internal State Distinction
This vulnerability occurs when an application fails to accurately track its own operational state. The system incorrectly assumes it's in…
CWE-400 Irmão
Uncontrolled Resource Consumption
This vulnerability occurs when an application fails to properly manage a finite resource, allowing an attacker to exhaust it and cause a…
CWE-404 Irmão
Improper Resource Shutdown or Release
This vulnerability occurs when a program fails to properly close or release a system resource—like a file handle, database connection, or…
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.