CWE-580: clone() Method Without super.clone()

Code Examples & CVEs

Demonstrative Examples

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.

BadJava

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();...                            }                      }

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-580 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-580, clone() Method Without super.clone(), throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address clone() Method Without super.clone() during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Static Analysis; recorded impacts include Unexpected State, and Quality Degradation. Use these source-defined anchors to turn CWE-580 into implementation, review, and verification checks for the affected component.

CWE-580: clone() Method Without super.clone() — MITRE CWE

Triage CWE-580 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-580, clone() Method Without super.clone(), has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-580

Apply MITRE's full root-cause mapping guidance when using CWE-580, clone() Method Without super.clone(). Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-580 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-580, clone() Method Without super.clone(). Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-580: clone() Method Without super.clone()?+

CWE-580: clone() Method Without super.clone() is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product contains a clone() method that does not call super.clone() to obtain the new object. All implementations of clone() should obtain the new object by calling super.clone(). If a class does not follow this convention, a subclass's clone() method will return an object of the wrong type.

What are the security consequences of clone() Method Without super.clone()?+

If exploited, CWE-580 (clone() Method Without super.clone()) it can compromise Integrity and Other, leading to outcomes such as Unexpected State and Quality Degradation.

How do you prevent or mitigate clone() Method Without super.clone()?+

Recommended mitigations for CWE-580 include: 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.

Which programming languages are affected by clone() Method Without super.clone()?+

CWE-580 commonly affects Java. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-580 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-580: clone() Method Without super.clone()

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description