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-2024-9701 Remote Code Execution in kedro-org/kedro — kedro-org/kedro 9.8 -2025-03-20
CVE-2024-12044 Remote Code Execution by Pickle Deserialization in open-mmlab/mmdetection — open-mmlab/mmdetection 9.8 -2025-03-20
CVE-2024-11039 Deserialization of Untrusted Data in binary-husky/gpt_academic — binary-husky/gpt_academic 8.8 -2025-03-20
CVE-2024-10190 Unauthenticated Remote Code Execution in ElasticRendezvousHandler in horovod/horovod — horovod/horovod 9.8 -2025-03-20
CVE-2024-8502 Remote Code Execution via Deserialization in modelscope/agentscope — modelscope/agentscope 9.8 -2025-03-20
CVE-2024-9053 Remote Code Execution in vllm-project/vllm — vllm-project/vllm 9.8 -2025-03-20
CVE-2024-10553 Jdbc Deserialization in h2oai/h2o-3 — h2oai/h2o-3 9.8 -2025-03-20
CVE-2024-12029 Remote Code Execution via Model Deserialization in invoke-ai/invokeai — invoke-ai/invokeai 8.8 -2025-03-20
CVE-2024-47552 Apache Seata (incubating): Deserialization of untrusted Data in jraft mode in Apache Seata Server — Apache Seata (incubating) 9.8 -2025-03-20
CVE-2025-27778 Applio allows unsafe deserialization in infer.py — Applio 9.8 -2025-03-19
CVE-2025-27779 Applio allows unsafe deserialization in model_blender.py — Applio 9.8 -2025-03-19
CVE-2025-27781 Applio allows unsafe deserialization in inference.py — Applio 9.8 -2025-03-19
CVE-2025-27780 Applio allows unsafe deserialization in model_information.py — Applio 9.8 -2025-03-19
CVE-2025-29783 vLLM Allows Remote Code Execution via Mooncake Integration — vllm 9.1 Critical2025-03-19
CVE-2024-13410 CozyStay <= 1.7.0 and TinySalt <= 3.9.0 - Unauthenticated PHP Object Injection in ajax_handler — CozyStay - Hotel Booking WordPress Theme 9.8 Critical2025-03-19
CVE-2025-2376 viames Pair Framework PHP Object UserRemember.php getCookieContent deserialization — Pair Framework 7.3 High2025-03-17
CVE-2025-26921 WordPress Booking and Rental Manager Plugin <= 2.2.6 - PHP Object Injection vulnerability — Booking and Rental Manager 8.8 High2025-03-15
CVE-2025-2000 Qiskit SDK code execution — Qiskit SDK 9.8 Critical2025-03-14
CVE-2024-13824 CiyaShop - Multipurpose WooCommerce Theme <= 4.19.0 - Unauthenticated PHP Object Injection — CiyaShop - Multipurpose WooCommerce Theme 9.8 Critical2025-03-14
CVE-2024-10942 All in One WP Migration <= 7.89 - Unauthenticated PHP Object Injection — All-in-One WP Migration and Backup 7.5 High2025-03-13
CVE-2025-27925 Nintex Automation 代码问题漏洞 — Automation 8.5 High2025-03-10
CVE-2024-13906 Gallery by BestWebSoft – Customizable Image and Photo Galleries for WordPress <= 4.7.3 - Authenticated (Administrator+) PHP Object Injection — Gallery by BestWebSoft – Customizable Image and Photo Galleries for WordPress 7.2 High2025-03-07
CVE-2025-2043 LinZhaoguan pb-cms Add New Topic admin#themes deserialization — pb-cms 4.7 Medium2025-03-06
CVE-2024-12742 Deserialization of Untrusted Data Vulnerability in NI G Web Development Software — G Web Development Software 7.8 High2025-03-06
CVE-2024-13787 VEDA - MultiPurpose WordPress Theme <= 4.2 - Authenticated (Subscriber+) PHP Object Injection — VEDA - MultiPurpose WordPress Theme 9.8 Critical2025-03-05
CVE-2024-13777 ZoomSounds - WordPress Wave Audio Player with Playlist <= 6.91 - Unauthenticated PHP Object Injection — ZoomSounds - WordPress Wave Audio Player with Playlist 8.1 High2025-03-05
CVE-2025-0956 WooCommerce Recover Abandoned Cart <= 24.4.0 - Unauthenticated PHP Object Injection — WooCommerce Recover Abandoned Cart 8.1 High2025-03-05
CVE-2025-0912 GiveWP – Donation Plugin and Fundraising Platform <= 3.19.4 - Unauthenticated PHP Object Injection — GiveWP – Donation Plugin and Fundraising Platform 9.8 Critical2025-03-04
CVE-2024-47092 Insecure deserialization and improper certificate validation in Checkmk Exchange plugin check-mk-api 9.8 -2025-03-03
CVE-2025-26967 WordPress Events Calendar for GeoDirectory plugin <= 2.3.14 - PHP Object Injection vulnerability — Events Calendar for GeoDirectory 8.8 High2025-03-03

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