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-2025-62420 DataEase vulnerable to remote code execution via H2 JDBC driver bypass — dataease 8.1AIHighAI2025-10-17
CVE-2025-49655 Keras 安全漏洞 — Keras 9.8 Critical2025-10-17
CVE-2025-54539 Apache ActiveMQ NMS AMQP Client: Deserialization of Untrusted Data — Apache ActiveMQ NMS AMQP Client 9.8AICriticalAI2025-10-16
CVE-2025-59287 Windows Server Update Service (WSUS) Remote Code Execution Vulnerability — Windows Server 2012 9.8 Critical2025-10-14
CVE-2025-59285 Azure Monitor Agent Elevation of Privilege Vulnerability — Azure Monitor 7.0 High2025-10-14
CVE-2025-59237 Microsoft SharePoint Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High2025-10-14
CVE-2025-11622 Ivanti Endpoint Manager 代码问题漏洞 — Endpoint Manager 7.8 High2025-10-13
CVE-2025-35051 Newforma Project Center Server (NPCS) .NET unauthenticated deserialization — Project Center 9.8 Critical2025-10-09
CVE-2025-35050 Newforma Info Exchange (NIX) .NET unauthenticated deserialization — Project Center 9.8 Critical2025-10-09
CVE-2025-11346 ILIAS Base64 Decoding unserialize deserialization — ILIAS 6.3 Medium2025-10-06
CVE-2025-11345 ILIAS Test Import unserialize deserialization — ILIAS 5.5 Medium2025-10-06
CVE-2025-10363 Unauthenticated RCE via .NET Deserialization in Topal Finance Software — Topal Finanzbuchhaltung 9.8AICriticalAI2025-10-06
CVE-2025-61765 python-socketio vulnerable to arbitrary Python code execution (RCE) through malicious pickle deserialization in certain multi-server deployments — python-socketio 6.4 Medium2025-10-06
CVE-2023-49886 IBM Transformation Extender Advanced code execution — Transformation Extender Advanced 9.8 Critical2025-10-06
CVE-2025-11273 LaChatterie Verger provider.ts redirectToAuthorization deserialization — Verger 6.3 Medium2025-10-04
CVE-2025-61677 DataChain: Deserialization of Untrusted Data from Environment Variables — datachain 2.5 Low2025-10-03
CVE-2025-61622 Apache Fory, Apache Fory: Python RCE via unguarded pickle fallback serializer in pyfory — Apache Fory 9.8AICriticalAI2025-10-01
CVE-2025-11135 pmTicket Project-Management-Software Cookie class.database.php loadLanguage deserialization — Project-Management-Software 7.3 High2025-09-29
CVE-2025-10975 GuanxingLu vlarl ZeroMQ reasoning_server.py run_reasoning_server deserialization — vlarl 6.3 Medium2025-09-25
CVE-2025-10974 giantspatula SewKinect Endpoint calculate pickle.loads deserialization — SewKinect 6.3 Medium2025-09-25
CVE-2025-10965 LazyAGI LazyLLM server.py lazyllm_call deserialization — LazyLLM 6.3 Medium2025-09-25
CVE-2025-10950 geyang ml-logger Ping server.py log_handler deserialization — ml-logger 6.3 Medium2025-09-25
CVE-2025-48459 Apache IoTDB: Deserialization of untrusted Data — Apache IoTDB 9.8AICriticalAI2025-09-24
CVE-2025-26399 SolarWinds Web Help Desk Deserialization of Untrusted Data Privilege Escalation Vulnerability — Web Help Desk 9.8 Critical2025-09-23
CVE-2025-53465 WordPress GSheets Connector Plugin <= 1.1.1 - PHP Object Injection Vulnerability — GSheets Connector 7.2 High2025-09-22
CVE-2025-57919 WordPress ConveyThis plugin <= 269.1 - PHP Object Injection vulnerability — ConveyThis 7.2 High2025-09-22
CVE-2025-58662 WordPress Awesome Support plugin <= 6.3.5 - Deserialization of untrusted data vulnerability — Awesome Support 7.2 High2025-09-22
CVE-2025-10771 jeecgboot JimuReport DB2 JDBC testConnection deserialization — JimuReport 6.3 Medium2025-09-21
CVE-2025-10770 jeecgboot JimuReport MySQL JDBC testConnection deserialization — JimuReport 6.3 Medium2025-09-21
CVE-2025-10769 h2oai h2o-3 H2 JDBC Driver ImportSQLTable deserialization — h2o-3 6.3 Medium2025-09-21

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