CWE-568 Variant Draft

finalize() Method Without super.finalize()

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

Definition

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.

Auswirkungen in der Praxis

Real-world CVEs caused by CWE-568

Bisher sind in MITREs Katalog keine öffentlichen CVE-Referenzen mit dieser CWE verknüpft.

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

1
Identifiziere einen Codepfad, der nicht vertrauenswürdige Eingaben ohne Validierung verarbeitet.
2
Erzeuge eine Payload, die das unsichere Verhalten auslöst — Injection, Traversal, Overflow oder Logik-Missbrauch.
3
Liefere die Payload über einen normalen Request aus und beobachte die Reaktion der Anwendung.
4
Iteriere, bis die Antwort Daten preisgibt, Angreifer-Code ausführt oder Berechtigungen eskaliert.

Verwundbares Codebeispiel

Vulnerable Java

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

Verwundbar Java

protected void finalize() {
  	discardNative();
  }

Sicheres Codebeispiel

Secure pseudo

Sicher 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.

Präventions-Checkliste

How to prevent CWE-568

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

Erkennungssignale

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

Häufig gestellte Fragen

Frequently asked questions

Was ist CWE-568?

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

Wie gravierend ist CWE-568?

MITRE hat für diese Schwachstelle keine Exploit-Wahrscheinlichkeit veröffentlicht. Behandle sie als mittlere Auswirkung, bis dein Threat Model anderes belegt.

Welche Sprachen oder Plattformen sind von CWE-568 betroffen?

MITRE lists the following affected platforms: Java.

Wie kann ich CWE-568 verhindern?

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

Wie erkennt und behebt Plexicus CWE-568?

Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-568 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.

Wo erfahre ich mehr über CWE-568?

MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/568.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.

Verwandte Schwachstellen

Weaknesses related to CWE-568

CWE-459 Parent

Bereit zu validieren, was zählt.

Plexicus ist Proof-Driven AppSec: validierte Funde, kontextuelles Verständnis und geprüfte Remediation — in Evidenz verankert, mit Ihnen gescoped.

Pentest buchen

finalize() Method Without super.finalize()

What is CWE-568?

Real-world CVEs caused by CWE-568

Angreiferpfad Schritt für Schritt

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

Bereit zu validieren, was zählt.

Prüfen Sie, ob AI Swarm Pentest zu Ihrer Umgebung passt.

Anfrage erhalten. Nächsten Schritt buchen.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`