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-48018 Deserialization of Untrusted Data — SEL-5030 acSELerator QuickSet Software 7.5 High2025-05-20
CVE-2025-32927 WordPress FoodBakery plugin <= 3.3 - PHP Object Injection vulnerability — FoodBakery 9.8 Critical2025-05-19
CVE-2025-32928 WordPress Altair theme <= 5.2.2 - PHP Object Injection vulnerability — Altair 9.8 Critical2025-05-19
CVE-2025-39348 WordPress Grand Restaurant WordPress theme <= 7.0 - PHP Object Injection vulnerability — Grand Restaurant 9.8 Critical2025-05-19
CVE-2025-39349 WordPress CiyaShop theme <= 4.18.0 - PHP Object Injection vulnerability — CiyaShop 9.8 Critical2025-05-19
CVE-2025-39354 WordPress Grand Conference theme <= 5.3 - PHP Object Injection vulnerability — Grand Conference 9.8 Critical2025-05-19
CVE-2025-39356 WordPress Foodbakery Sticky Cart plugin <= 3.2 - PHP Object Injection vulnerability — Foodbakery Sticky Cart 9.8 Critical2025-05-19
CVE-2025-39410 WordPress Smart Sections Theme Builder - WPBakery Page Builder Addon plugin <= 1.7.8 - PHP Object Injection vulnerability — Smart Sections Theme Builder - WPBakery Page Builder Addon 9.8 Critical2025-05-19
CVE-2025-47581 WordPress WordPress Events Calendar Registration & Tickets plugin <= 2.6.0 - PHP Object Injection vulnerability — WordPress Events Calendar Registration & Tickets 9.8 Critical2025-05-19
CVE-2025-47582 WordPress WPBot Pro Wordpress Chatbot <= 12.7.0 - PHP Object Injection Vulnerability — WPBot Pro Wordpress Chatbot 9.8 Critical2025-05-19
CVE-2025-4905 iop-apl-uw basestation3 QC.py load_qc_pickl deserialization — basestation3 5.3 Medium2025-05-19
CVE-2025-48134 WordPress WP Tabs plugin <= 2.2.12 - PHP Object Injection Vulnerability — WP Tabs 7.2 High2025-05-16
CVE-2025-4742 XU-YIJIE grpo-flat grpo_vanilla.py main deserialization — grpo-flat 5.3 Medium2025-05-16
CVE-2025-4740 BeamCtrl Airiana coef deserialization — Airiana 5.3 Medium2025-05-16
CVE-2025-47784 Emlog vulnerable to Deserialization of Untrusted Data — emlog 7.3AIHighAI2025-05-15
CVE-2025-4701 VITA-MLLM Freeze-Omni utils.py torch.load deserialization — Freeze-Omni 5.3 Medium2025-05-15
CVE-2025-47292 Cap Collectif vulnerable to insecure deserialization leading to remote code execution — cap-collectif 9.8AICriticalAI2025-05-14
CVE-2025-3623 Uncanny Automator <= 6.4.0.1 - Unauthenticated PHP Object Injection in automator_api_decode_message Function — Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin 9.1 Critical2025-05-14
CVE-2025-30384 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 7.4 High2025-05-13
CVE-2025-30382 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 7.8 High2025-05-13
CVE-2025-30378 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 7.0 High2025-05-13
CVE-2025-42999 Insecure Deserialization in SAP NetWeaver (Visual Composer development server) — SAP NetWeaver (Visual Composer development server) 9.1 Critical2025-05-13
CVE-2025-30012 Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit) — SAP Supplier Relationship Management (Live Auction Cockpit) 10.0 Critical2025-05-13
CVE-2025-46738 Deserialization of Untrusted Data — SEL-5033 acSELerator RTAC Software 6.6 Medium2025-05-12
CVE-2025-47732 Microsoft Dataverse Remote Code Execution Vulnerability — Microsoft Dataverse 8.7 High2025-05-08
CVE-2025-47683 WordPress WP Maintenance plugin <= 6.1.9.7 - PHP Object Injection Vulnerability — WP Maintenance 7.2 High2025-05-07
CVE-2025-47629 WordPress WP-CRM System plugin <= 3.4.5 - PHP Object Injection vulnerability — WP-CRM System 7.2 High2025-05-07
CVE-2025-0855 PGS Core <= 5.8.0 - Unauthenticated PHP Object Injection — PGS Core 9.8 Critical2025-05-06
CVE-2025-30165 Remote Code Execution Vulnerability in vLLM Multi-Node Cluster Configuration — vllm 8.0 High2025-05-06
CVE-2025-43852 GHSL-2025-022_Retrieval-based-Voice-Conversion-WebUI — Retrieval-based-Voice-Conversion-WebUI 9.8AICriticalAI2025-05-05

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