CWE-498: Cloneable Class Containing Sensitive Information

Code Examples & CVEs

Demonstrative Examples

The following example demonstrates the weakness.

Make classes uncloneable by defining a clone function like:

BadJava

public class CloneClient {                         public CloneClient() //throwsjava.lang.CloneNotSupportedException {                                                                 Teacher t1 = new Teacher("guddu","22,nagar road");//...// Do some stuff to remove the teacher.Teacher t2 = (Teacher)t1.clone();System.out.println(t2.name);                            }public static void main(String args[]) {                                                                 new CloneClient();                            }                      }class Teacher implements Cloneable {                                                     public Object clone() {                                                                 try {return super.clone();}catch (java.lang.CloneNotSupportedException e) {                                                                             throw new RuntimeException(e.toString());                                  }                            }public String name;public String clas;public Teacher(String name,String clas) {                                                                 this.name = name;this.clas = clas;                            }                      }

The following example demonstrates the weakness.

Make classes uncloneable by defining a clone function like:

GoodJava

public final void clone() throws java.lang.CloneNotSupportedException {throw new java.lang.CloneNotSupportedException();}

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-498 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-498, Cloneable Class Containing Sensitive Information, 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 Cloneable Class Containing Sensitive Information during Implementation

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

CWE-498: Cloneable Class Containing Sensitive Information — MITRE CWE

Triage CWE-498 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-498, Cloneable Class Containing Sensitive Information, 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-498

Apply MITRE's full root-cause mapping guidance when using CWE-498, Cloneable Class Containing Sensitive Information. 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-498 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-498, Cloneable Class Containing Sensitive Information. 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-498: Cloneable Class Containing Sensitive Information?+

CWE-498: Cloneable Class Containing Sensitive Information is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class. Cloneable classes are effectively open classes, since data cannot be hidden in them. Classes that do not explicitly deny cloning can be cloned by any other class without running the constructor.

What are the security consequences of Cloneable Class Containing Sensitive Information?+

If exploited, CWE-498 (Cloneable Class Containing Sensitive Information) it can compromise Access Control, leading to outcomes such as Bypass Protection Mechanism.

How do you prevent or mitigate Cloneable Class Containing Sensitive Information?+

Recommended mitigations for CWE-498 include: If you do make your classes clonable, ensure that your clone method is final and throw super.clone().

Which programming languages are affected by Cloneable Class Containing Sensitive Information?+

CWE-498 commonly affects C++, Java, C# and Object-Oriented. 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-498 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-498: Cloneable Class Containing Sensitive Information

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods