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.)
CWE-460 Base Rascunho
Improper Cleanup on Thrown Exception
This vulnerability occurs when a program fails to properly restore its state or release resources after an exception is thrown, leaving the application in an inconsistent or unexpected condition.
Definição
What is CWE-460?
This vulnerability occurs when a program fails to properly restore its state or release resources after an exception is thrown, leaving the application in an inconsistent or unexpected condition.
In complex functions or loops, temporary resources like file handles, database connections, or memory allocations often need careful management. When an exception interrupts the normal execution flow, cleanup code that runs during a successful path might be skipped entirely. This leaves resources dangling or data in a partially modified state, which can cause crashes, data corruption, or security issues like information disclosure.
Managing this at scale is difficult; an ASPM like Plexicus can help you track and remediate these flaws across your entire stack. While SAST tools can identify risky patterns, Plexicus uses AI to analyze execution paths and suggest specific fixes—such as implementing finally blocks or using try-with-resources constructs—saving hours of manual code review and preventing unstable application behavior.
Impacto no mundo real
Real-world CVEs caused by CWE-460
Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.
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 Java
The following example demonstrates the weakness.
public class foo {
public static final void main( String args[] ) {
boolean returnValue;
returnValue=doStuff();
}
public static final boolean doStuff( ) {
boolean threadLock;
boolean truthvalue=true;
try {
while(
```
//check some condition*
) {
```
threadLock=true; //do some stuff to truthvalue
threadLock=false;
}
}
catch (Exception e){
System.err.println("You did something bad");
if (something) return truthvalue;
}
return truthvalue;
}
} 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-460
- Implementation If one breaks from a loop or function by throwing an exception, make sure that cleanup happens or that you should exit the program. Use throwing exceptions sparsely.
Sinais de deteção
How to detect CWE-460
CWE-460
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-460?
Qual a gravidade do CWE-460?
Que linguagens ou plataformas são afetadas pelo CWE-460?
Como posso prevenir o CWE-460?
Como é que o Plexicus deteta e corrige o CWE-460?
Onde posso saber mais sobre o CWE-460?
Frequently asked questions
O que é o CWE-460?
This vulnerability occurs when a program fails to properly restore its state or release resources after an exception is thrown, leaving the application in an inconsistent or unexpected condition.
Qual a gravidade do CWE-460?
A MITRE classifica a probabilidade de exploração como Média — a exploração é realista mas normalmente requer condições específicas.
Que linguagens ou plataformas são afetadas pelo CWE-460?
MITRE lists the following affected platforms: C, C++, Java, C#.
Como posso prevenir o CWE-460?
If one breaks from a loop or function by throwing an exception, make sure that cleanup happens or that you should exit the program. Use throwing exceptions sparsely.
Como é que o Plexicus deteta e corrige o CWE-460?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-460 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-460?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/460.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-460
CWE-459 Pai
Incomplete Cleanup
This vulnerability occurs when an application fails to properly remove temporary files, data structures, or system resources after they…
CWE-226 Irmão
Sensitive Information in Resource Not Removed Before Reuse
This vulnerability occurs when a system releases a resource like memory or a file for reuse but fails to erase the sensitive data it…
CWE-568 Irmão
finalize() Method Without super.finalize()
This vulnerability occurs when a Java class overrides the finalize() method but fails to call super.finalize() within it.
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ê.