1 vulnerabilities classified as CWE-499 (可序列化的类中包含敏感信息). AI Chinese analysis included.
CWE-499 represents a design weakness where a class containing sensitive data fails to explicitly prevent serialization, effectively rendering its internal state publicly accessible. This vulnerability arises because Java’s default serialization mechanism allows any other class to serialize the object, bypassing encapsulation controls that would normally restrict data access. Attackers typically exploit this by instantiating the vulnerable class, serializing it to a stream or file, and then deserializing it in a separate context to extract confidential information such as credentials or personal identifiers. To mitigate this risk, developers must implement the Externalizable interface or define private readObject and writeObject methods to control the serialization process. Alternatively, marking sensitive fields as transient ensures they are excluded from the serialized output, thereby preserving data confidentiality even if the class structure is compromised.
class PatientRecord { private String name; private String socialSecurityNum; public Patient(String name,String ssn) { this.SetName(name); this.SetSocialSecurityNumber(ssn); } }| CVE ID | Title | CVSS | Severity | Published |
|---|---|---|---|---|
| CVE-2024-5657 | CraftCMS Plugin - Two-Factor Authentication - Password Hash Disclosure — CraftCMS Plugin - Two-Factor Authentication | 3.7 | Low | 2024-06-06 |
Vulnerabilities classified as CWE-499 (可序列化的类中包含敏感信息) represent 1 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.