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-43851 GHSL-2025-021_Retrieval-based-Voice-Conversion-WebUI — Retrieval-based-Voice-Conversion-WebUI 9.8AICriticalAI2025-05-05
CVE-2025-43850 GHSL-2025-020_Retrieval-based-Voice-Conversion-WebUI — Retrieval-based-Voice-Conversion-WebUI 9.8AICriticalAI2025-05-05
CVE-2025-43849 GHSL-2025-019_Retrieval-based-Voice-Conversion-WebUI — Retrieval-based-Voice-Conversion-WebUI 9.8AICriticalAI2025-05-05
CVE-2025-43848 GHSL-2025-018_Retrieval-based-Voice-Conversion-WebUI — Retrieval-based-Voice-Conversion-WebUI 9.8AICriticalAI2025-05-05
CVE-2025-43847 GHSL-2025-017_Retrieval-based-Voice-Conversion-WebUI — Retrieval-based-Voice-Conversion-WebUI 9.8AICriticalAI2025-05-05
CVE-2025-43846 GHSL-2025-016_Retrieval-based-Voice-Conversion-WebUI — Retrieval-based-Voice-Conversion-WebUI 9.8AICriticalAI2025-05-05
CVE-2025-4260 zhangyanbo2007 youkefu TemplateController.java impsave deserialization — youkefu 4.3 Medium2025-05-05
CVE-2025-46567 LLaMA-Factory Allows Arbitrary Code Execution via Unsafe Deserialization in Ilamafy_baichuan2.py — LLaMA-Factory 6.1 Medium2025-05-01
CVE-2025-23254 NVIDIA TensorRT-LLM 代码问题漏洞 — TensorRT-LLM 8.8 High2025-05-01
CVE-2025-32444 vLLM Vulnerable to Remote Code Execution via Mooncake Integration — vllm 10.0 Critical2025-04-30
CVE-2025-34491 GFI MailEssentials < 21.8 MultiNode Insecure Deserialization — MailEssentials 8.8 High2025-04-28
CVE-2025-34489 GFI MailEssentials < 21.8 Local Privilege Escalation — MailEssentials 7.8 High2025-04-28
CVE-2023-35815 DevExpress 安全漏洞 — DevExpress 3.5 Low2025-04-28
CVE-2023-35814 DevExpress 安全漏洞 — DevExpress 3.5 Low2025-04-28
CVE-2025-2105 Jupiter X Core <= 4.8.11 - Unauthenticated PHP Object Injection via PHAR — Jupiter X Core 8.1 High2025-04-26
CVE-2025-3935 ScreenConnect Exposure to ASP.NET ViewState Code Injection — ScreenConnect 8.1 High2025-04-25
CVE-2025-46473 WordPress Social Counter plugin <= 2.0.5 - PHP Object Injection Vulnerability — Social Counter 7.2 High2025-04-24
CVE-2025-46481 WordPress Flickr Shortcode Importer plugin <= 2.2.3 - PHP Object Injection Vulnerability — Flickr Shortcode Importer 7.2 High2025-04-24
CVE-2025-23249 NVIDIA Nemo Framework 代码问题漏洞 — NeMo Framework 7.6 High2025-04-22
CVE-2025-32434 PyTorch: `torch.load` with `weights_only=True` leads to remote code execution — pytorch 8.8 -2025-04-18
CVE-2025-29953 Apache ActiveMQ NMS OpenWire Client: deserialization allowlist bypass — Apache ActiveMQ NMS OpenWire Client 9.8 -2025-04-18
CVE-2025-27286 WordPress Saoshyant Slider Plugin <= 3.0 - PHP Object Injection vulnerability — Saoshyant Slider 9.8 Critical2025-04-17
CVE-2025-27287 WordPress SS Quiz Plugin <= 2.0.5 - PHP Object Injection vulnerability — SS Quiz 9.8 Critical2025-04-17
CVE-2025-32571 WordPress TuriTop Booking System Plugin <= 1.0.10 - PHP Object Injection vulnerability — TuriTop Booking System 8.8 High2025-04-17
CVE-2025-32572 WordPress Kata Plus Plugin <= 1.5.3 - PHP Object Injection vulnerability — Kata Plus 9.8 Critical2025-04-17
CVE-2025-32647 WordPress Question Answer plugin <= 1.2.73 - PHP Object Injection vulnerability — Question Answer 8.8 High2025-04-17
CVE-2025-32658 WordPress HelpGent plugin <= 2.2.5 - PHP Object Injection vulnerability — HelpGent 9.8 Critical2025-04-17
CVE-2025-32662 WordPress uListing plugin <= 2.2.0 - Deserialization of untrusted data vulnerability — uListing 8.8 High2025-04-17
CVE-2025-32686 WordPress Team Members plugin <= 3.4.4 - PHP Object Injection Vulnerability — Team Members 8.8 High2025-04-17
CVE-2025-39527 WordPress Rating by BestWebSoft plugin <= 1.7 - PHP Object Injection Vulnerability — Rating by BestWebSoft 8.8 High2025-04-17

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