CWE-583 Variant Incomplete

finalize() Method Declared Public

This vulnerability occurs when a Java class declares its finalize() method as public, violating secure coding practices for mobile code.

Definition

What is CWE-583?

This vulnerability occurs when a Java class declares its finalize() method as public, violating secure coding practices for mobile code.
In Java, the finalize() method is a special method called by the garbage collector before an object is destroyed. Declaring it as public breaks the intended contract, as this method should only ever be invoked automatically by the JVM's garbage collection process, not directly by application code. Explicit calls to finalize() are strongly discouraged and are a common source of errors and unpredictable behavior. For mobile code, such as applets or frameworks where code is downloaded and executed remotely, this flaw becomes a direct security threat. An attacker could exploit the publicly accessible finalize() method to trigger malicious logic, interfere with object cleanup, or cause a denial of service by manually invoking garbage collection routines. The secure practice is to always declare finalize() as protected, and within it, only call super.finalize().
Real-world impact

Real-world CVEs caused by CWE-583

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable Java

The following Java Applet code mistakenly declares a public finalize() method.

Vulnerable Java
public final class urlTool extends Applet {
  	public void finalize() {
  		...
  	}
  	...
  }
Secure code example

Secure pseudo

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.
Prevention checklist

How to prevent CWE-583

  • Implementation If you are using finalize() as it was designed, there is no reason to declare finalize() with anything other than protected access.
Detection signals

How to detect CWE-583

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

Plexicus auto-fix

Plexicus auto-detects CWE-583 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Frequently asked questions

Frequently asked questions

What is CWE-583?

This vulnerability occurs when a Java class declares its finalize() method as public, violating secure coding practices for mobile code.

How serious is CWE-583?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-583?

MITRE lists the following affected platforms: Java.

How can I prevent CWE-583?

If you are using finalize() as it was designed, there is no reason to declare finalize() with anything other than protected access.

How does Plexicus detect and fix CWE-583?

Plexicus's SAST engine matches the data-flow signature for CWE-583 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-583?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/583.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-583

CWE-668 Parent

Exposure of Resource to Wrong Sphere

This vulnerability occurs when an application unintentionally makes a resource accessible to users or systems that should not have…

CWE-1189 Sibling

Improper Isolation of Shared Resources on System-on-a-Chip (SoC)

This vulnerability occurs when a System-on-a-Chip (SoC) fails to properly separate shared hardware resources between secure (trusted) and…

CWE-1282 Sibling

Assumed-Immutable Data is Stored in Writable Memory

This vulnerability occurs when data that should be permanent and unchangeable—like a bootloader, device IDs, or one-time configuration…

CWE-1327 Sibling

Binding to an Unrestricted IP Address

This vulnerability occurs when software or a service is configured to bind to the IP address 0.0.0.0 (or :: in IPv6), which acts as a…

CWE-1331 Sibling

Improper Isolation of Shared Resources in Network On Chip (NoC)

This vulnerability occurs when a Network on Chip (NoC) fails to properly separate its internal, shared resources—like buffers, switches,…

CWE-134 Sibling

Use of Externally-Controlled Format String

This vulnerability occurs when a program uses a format string from an untrusted, external source (like user input, a network packet, or a…

CWE-200 Sibling

Exposure of Sensitive Information to an Unauthorized Actor

This weakness occurs when an application unintentionally reveals sensitive data to someone who shouldn't have access to it.

CWE-374 Sibling

Passing Mutable Objects to an Untrusted Method

This vulnerability occurs when a function receives a direct reference to mutable data, such as an object or array, instead of a safe copy…

CWE-375 Sibling

Returning a Mutable Object to an Untrusted Caller

This vulnerability occurs when a method directly returns a reference to its internal mutable data, allowing untrusted calling code to…

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.