CWE-580 Variant Draft

clone() Method Without super.clone()

This vulnerability occurs when a class's clone() method creates a new object directly instead of calling super.clone().

Definition

What is CWE-580?

This vulnerability occurs when a class's clone() method creates a new object directly instead of calling super.clone().
In Java, the proper way to implement the clone() method is to always start with a call to super.clone(). This call travels up the inheritance chain to Object.clone(), which performs the essential bitwise copy that establishes the correct object type and internal structure. Skipping this step and instantiating the object manually (e.g., using 'new') breaks the inherited cloning contract. When a parent class fails to call super.clone(), any subclass that inherits and uses its clone() method will receive an object of the parent's type, not its own. This causes a ClassCastException when the returned object is cast to the subclass type, leading to runtime failures. Adhering to the super.clone() convention ensures the cloning mechanism works correctly throughout the entire class hierarchy.
Real-world impact

Real-world CVEs caused by CWE-580

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 two classes demonstrate a bug introduced by not calling super.clone(). Because of the way Kibitzer implements clone(), FancyKibitzer's clone method will return an object of type Kibitzer instead of FancyKibitzer.

Vulnerable Java 
public class Kibitzer {
  		public Object clone() throws CloneNotSupportedException {
  				Object returnMe = new Kibitzer();
  				...
  		}
  }
  public class FancyKibitzer extends Kibitzer{
  		public Object clone() throws CloneNotSupportedException {
  				Object returnMe = super.clone();
  				...
  		}
  }
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-580

  • Implementation Call super.clone() within your clone() method, when obtaining a new object.
  • Implementation In some cases, you can eliminate the clone method altogether and use copy constructors.
Detection signals

How to detect CWE-580

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

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-580?

This vulnerability occurs when a class's clone() method creates a new object directly instead of calling super.clone().

How serious is CWE-580?

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-580?

MITRE lists the following affected platforms: Java.

How can I prevent CWE-580?

Call super.clone() within your clone() method, when obtaining a new object. In some cases, you can eliminate the clone method altogether and use copy constructors.

How does Plexicus detect and fix CWE-580?

Plexicus's SAST engine matches the data-flow signature for CWE-580 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-580?

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

Related weaknesses

Weaknesses related to CWE-580

CWE-664 Parent

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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…

Resources

Further reading

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.