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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

2488 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)
Integrity Modify 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.
Availability DoS: 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.
Other Varies 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, Implementation If 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.
Implementation When 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.
Implementation Explicitly define a final object() to prevent deserialization.
Architecture and Design, Implementation Make 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.
Implementation Avoid 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 ID Title CVSS Severity Published
CVE-2021-42550 RCE from attacker with configuration edit priviledges through JNDI lookup — logback 6.6 Medium 2021-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 High 2021-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 High 2021-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 Critical 2021-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 High 2021-10-06
CVE-2021-41110 CWL Viewer: deserialization of untrusted data can lead to complete takeover by an attacker — cwlviewer 9.1 Critical 2021-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
CVE-2021-39207 Deserialization of Untrusted Data in parlai — ParlAI 8.4 High 2021-09-10
CVE-2021-24040 parlai 代码问题漏洞 — ParlAI 7.2 - 2021-09-10
CVE-2021-32568 Deserialization of Untrusted Data in zmister2016/mrdoc — zmister2016/mrdoc 7.8 - 2021-09-06
CVE-2021-35218 Chart Endpoint Deserialization of Untrusted Data Remote Code Execution Vulnerability — Patch Manager 8.9 High 2021-09-01
CVE-2021-35216 Deserialization of Untrusted Data in Resource Controls Remote Code Execution — Patch Manager 8.9 High 2021-09-01
CVE-2021-35215 ActionPluginBaseView Deserialization of Untrusted Data RCE — Orion Platform 8.9 High 2021-09-01
CVE-2021-39132 YAML deserialization can run untrusted code — rundeck 8.8 High 2021-08-30
CVE-2021-24579 Bold Page Builder < 3.1.6 - PHP Object Injection — Bold Page Builder 8.8 - 2021-08-30
CVE-2021-21869 3s-smart Software Solutions CODESYS Development System 代码问题漏洞 — CODESYS 7.8 - 2021-08-25

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