CWEweakness
CWE-498 Cloneable Class Containing Sensitive Information
Medium
Official page ↗
- Abstraction
- Variant
- Structure
- Simple
- Status
- Draft
- Likelihood of exploit
- Medium
- Languages
- C#, C++, Java, Object-Oriented
- CWE version
- 5.0
Description
The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class.
Common consequences
• Access Control, Confidentiality: Bypass Protection Mechanism, Read Application Data — A class that does not explicitly deny cloning can be cloned by any other class without running the constructor. Cloneable classes are effectively open classes, since data cannot be hidden in the. This is also dangerous since the constructor may perform security-related checks. By allowing the object to be cloned, those checks may be bypassed.
Potential mitigations
• [Implementation] If you do make your classes clonable, ensure that your clone method is final and throw super.clone().
Detection methods
• Automated Static Analysis: 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.)
Related
Can precede · CWE (1)
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness
Child of · CWE (1)
- CWE-668 Exposure of Resource to Wrong Sphere weakness
Referenced by CWE · has member (1)
- CWE-884 CWE Cross-section view