CWE-568 Variante Borrador

finalize() Method Without super.finalize()

This vulnerability occurs when a Java class overrides the finalize() method but fails to call super.finalize() within it.

Definición

What is CWE-568?

This vulnerability occurs when a Java class overrides the finalize() method but fails to call super.finalize() within it.

In Java, the finalize() method is called by the garbage collector before an object is destroyed. If you override this method in a subclass and omit the call to super.finalize(), you break the cleanup chain. This prevents the parent class from performing its own essential cleanup operations, which can lead to resource leaks like unclosed file handles or database connections. To prevent this, always include super.finalize() as the final action in your overridden finalize method. While modern Java development often recommends using cleaner alternatives like try-with-resources or AutoCloseable for resource management, maintaining the super.finalize() call remains a critical defensive practice in legacy code or when overriding finalize is unavoidable.

Impacto en el mundo real

Real-world CVEs caused by CWE-568

Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

1
Identifica una ruta de código que maneje entrada no confiable sin validación.
2
Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.
3
Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.
4
Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.

Ejemplo de código vulnerable

Vulnerable Java

The following method omits the call to super.finalize().

Vulnerable Java

protected void finalize() {
  	discardNative();
  }

Ejemplo de código seguro

Secure pseudo

Seguro 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 prevención

How to prevent CWE-568

Implementation Call the super.finalize() method.
Testing Use static analysis tools to spot such issues in your code.

Señales de detección

How to detect CWE-568

Automated Static Analysis High

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-568

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.

Request AI Swarm Pentest

Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-568?

This vulnerability occurs when a Java class overrides the finalize() method but fails to call super.finalize() within it.

¿Qué gravedad tiene CWE-568?

MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.

¿Qué lenguajes o plataformas se ven afectados por CWE-568?

MITRE lists the following affected platforms: Java.

¿Cómo puedo prevenir CWE-568?

Call the super.finalize() method. Use static analysis tools to spot such issues in your code.

¿Cómo detecta y corrige Plexicus CWE-568?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-568 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.

¿Dónde puedo aprender más sobre CWE-568?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/568.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-568

CWE-459 Padre

Listo para validar lo que importa.

Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.

Reservar Pentest

finalize() Method Without super.finalize()

What is CWE-568?

Real-world CVEs caused by CWE-568

Ruta del atacante paso a paso

Vulnerable Java

Secure pseudo

How to prevent CWE-568

How to detect CWE-568

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-568

Incomplete Cleanup

Sensitive Information in Resource Not Removed Before Reuse

Improper Cleanup on Thrown Exception

Further reading

Listo para validar lo que importa.

Comprueba si el AI Swarm Pentest encaja en tu entorno.

Solicitud recibida. Reserva el siguiente paso.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`