Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-502 (可信数据的反序列化) — Vulnerability Class 1687

1687 vulnerabilities classified as CWE-502 (可信数据的反序列化). AI Chinese analysis included.

CWE-502 represents a critical security weakness where applications deserialize untrusted data without validating its integrity or structure. Attackers typically exploit this vulnerability by crafting malicious serialized objects that, when processed by the application, trigger unintended code execution or logic flaws. This often leads to remote code execution, denial of service, or privilege escalation, as the deserialization process may instantiate dangerous classes or invoke unsafe methods. To mitigate this risk, developers must strictly avoid deserializing data from untrusted sources. Instead, they should implement robust input validation, use allowlists for permitted data types, or adopt safer serialization formats like JSON that do not inherently support arbitrary object instantiation. Additionally, employing cryptographic signatures to verify data authenticity before deserialization ensures that only trusted, unaltered payloads are processed, effectively neutralizing the threat of malicious object injection.

MITRE CWE Description
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Common Consequences (3)
IntegrityModify Application Data, Unexpected State
Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.
AvailabilityDoS: Resource Consumption (CPU)
If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.
OtherVaries by Context
The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform una…
Mitigations (5)
Architecture and Design, ImplementationIf available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
ImplementationWhen deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
ImplementationExplicitly define a final object() to prevent deserialization.
Architecture and Design, ImplementationMake fields transient to protect them from deserialization. An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.
ImplementationAvoid having unnecessary types or gadgets (a sequence of instances and method invocations that can self-execute during the deserialization process, often found in libraries) available that can be leveraged for malicious ends. This limits the potential for unintended or unauthorized types and gadgets to be leveraged by the attacker. Add only acceptable classes to an allowlist. Note: new gadgets are…
Examples (2)
This code snippet deserializes an object from a file and uses it as a UI button:
try { File file = new File("object.obj"); ObjectInputStream in = new ObjectInputStream(new FileInputStream(file)); javax.swing.JButton button = (javax.swing.JButton) in.readObject(); in.close(); }
Bad · Java
private final void readObject(ObjectInputStream in) throws java.io.IOException { throw new java.io.IOException("Cannot be deserialized"); }
Good · Java
In Python, the Pickle library handles the serialization and deserialization processes. In this example derived from [REF-467], the code receives and parses data, and afterwards tries to authenticate a user based on validating a token.
try { class ExampleProtocol(protocol.Protocol): def dataReceived(self, data): # Code that would be here would parse the incoming data # After receiving headers, call confirmAuth() to authenticate def confirmAuth(self, headers): try: token = cPickle.loads(base64.b64decode(headers['AuthToken'])) if not check_hmac(token['signature'], token['data'], getSecretKey()): raise AuthFail self.secure_data = token['data'] except: raise AuthFail }
Bad · Python
CVE IDTitleCVSSSeverityPublished
CVE-2022-24289 Deserialization of untrusted data in the Hessian Component of Apache Cayenne 4.1 with older Java versions — Apache Cayenne 8.8 -2022-02-11
CVE-2022-23307 A deserialization flaw in the Chainsaw component of Log4j 1 can lead to malicious code execution. — Apache Log4j 1.x 9.8 -2022-01-18
CVE-2022-23302 Deserialization of untrusted data in JMSSink in Apache Log4j 1.x — Apache Log4j 1.x 8.8 -2022-01-18
CVE-2021-43297 Dubbo Hessian cause RCE when parse error — Apache Dubbo 9.8 -2022-01-10
CVE-2021-42392 H2database代码问题漏洞 — h2 9.8 -2022-01-07
CVE-2022-21647 Deserialization of Untrusted Data in Codeigniter4 — CodeIgniter4 7.7 High2022-01-04
CVE-2021-20318 Red Hat Jboss Enterprise Application Platform 7 代码问题漏洞 — Artemis in EAP 7 7.2 -2021-12-23
CVE-2021-4118 Deserialization of Untrusted Data in pytorchlightning/pytorch-lightning — pytorchlightning/pytorch-lightning 7.8 -2021-12-23
CVE-2021-36336 Dell Wyse Management Suite代码问题漏洞 — Wyse Management Suite 9.8 Critical2021-12-21
CVE-2021-42550 RCE from attacker with configuration edit priviledges through JNDI lookup — logback 6.6 Medium2021-12-16
CVE-2021-4104 Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2 — Apache Log4j 1.x 7.5 -2021-12-14
CVE-2021-24857 ToTop Link <= 1.7.1 - Unauthenticated PHP Object Injection — ToTop Link 9.8 -2021-12-13
CVE-2021-44228 Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints — Apache Log4j2 9.9 -2021-12-10
CVE-2021-42130 Ivanti Avalanche 代码问题漏洞 — Ivanti Avalanche 8.8 -2021-12-07
CVE-2021-42127 Ivanti Avalanche 代码问题漏洞 — Ivanti Avalanche 9.8 -2021-12-07
CVE-2021-42125 Ivanti Avalanche 代码问题漏洞 — Ivanti Avalance 8.8 -2021-12-07
CVE-2021-43360 Sunnet eHRD - Insecure Deserialization — eHRD 8.8 High2021-12-01
CVE-2021-22095 Spring AMQP 代码问题漏洞 — Spring AMQP 6.5 -2021-11-30
CVE-2021-34992 Orckestra C1 CMS 代码问题漏洞 — C1 CMS 8.8 -2021-11-15
CVE-2021-26558 Deserialization of Untrusted Data — Apache ShardingSphere-UI 7.5 -2021-11-11
CVE-2021-42698 AzeoTech DAQFactory — DAQFactory 7.8 High2021-11-05
CVE-2021-22097 Spring AMQP 代码问题漏洞 — Spring AMQP 7.5 -2021-10-28
CVE-2021-40865 Unsafe Pre-Authentication Deserialization In Workers — Apache Storm 9.8 -2021-10-25
CVE-2021-40719 Adobe Connect Deserialization of Untrusted Data Remote Code Execution — Connect 9.8 -2021-10-21
CVE-2021-40720 Ops CLI Deserialization of Untrusted Data leads to Abritrary Code Execution — Ops-CLI 9.8 Critical2021-10-15
CVE-2021-33728 Siemens SINEC NMS 代码问题漏洞 — SINEC NMS 7.2 -2021-10-12
CVE-2021-41129 Authentication bypass in Pterodactyl — panel 8.1 High2021-10-06
CVE-2021-41110 CWL Viewer: deserialization of untrusted data can lead to complete takeover by an attacker — cwlviewer 9.1 Critical2021-10-01
CVE-2021-41616 Apache ddlutils 1.0 readobject vulnerability — Apache DB ddlutils 9.8 -2021-09-30
CVE-2021-37181 多款 Siemens 产品代码问题漏洞 — Cerberus DMS V4.0 10.0 -2021-09-14

Vulnerabilities classified as CWE-502 (可信数据的反序列化) represent 1687 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.