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-54686 WordPress Exertio Theme <= 1.3.2 - PHP Object Injection Vulnerability — Exertio 9.8 Critical2025-08-14
CVE-2025-47536 WordPress Content Egg plugin <= 7.0.0 - PHP Object Injection Vulnerability — Content Egg 7.2 High2025-08-14
CVE-2025-49869 WordPress Eventin Plugin <= 4.0.31 - PHP Object Injection Vulnerability — Eventin 8.8 High2025-08-14
CVE-2025-23303 NVIDIA NeMo Framework 代码问题漏洞 — NVIDIA NeMo Framework 7.8 High2025-08-13
CVE-2025-2180 Checkov by Prisma Cloud: Unsafe Deserialization of Terraform Files Allows Code Execution — Checkov by Prisma Cloud 8.8AIHighAI2025-08-13
CVE-2025-34153 Hyland OnBase < 17.0.2.87 .NET Remoting TCP Channel Unauthenticated RCE — OnBase 9.8AICriticalAI2025-08-13
CVE-2025-7384 Database for Contact Form 7, WPforms, Elementor forms <= 1.4.3 - Unauthenticated PHP Object Injection to Arbitrary File Deletion — Database for Contact Form 7, WPforms, Elementor forms 9.8 Critical2025-08-13
CVE-2025-49712 Microsoft SharePoint Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High2025-08-12
CVE-2025-53772 Web Deploy Remote Code Execution Vulnerability — Web Deploy 4.0 8.8 High2025-08-12
CVE-2025-55010 Kanboard Authenticated Admin Remote Code Execution via Unsafe Deserialization of Events — kanboard 9.1 Critical2025-08-12
CVE-2025-40759 Siemens多款产品 代码问题漏洞 — SIMATIC S7-PLCSIM V17 7.8 High2025-08-12
CVE-2024-54678 Siemens多款产品 代码问题漏洞 — SIMATIC PCS neo V4.1 8.2 High2025-08-12
CVE-2025-8747 Keras safe_mode bypass allows arbitrary code execution when loading a malicious model. — Keras 7.8AIHighAI2025-08-11
CVE-2025-53606 Apache Seata (incubating): Deserialization of untrusted Data in Apache Seata Server — Apache Seata (incubating) 9.8 -2025-08-08
CVE-2025-8708 Antabot White-Jotter com.gm.wj.config.ShiroConfiguration ShiroConfiguration.java CookieRememberMeManager deserialization — White-Jotter 5.0 Medium2025-08-08
CVE-2025-54886 skops: Card.get_model does not block arbitrary code execution — skops 8.4 High2025-08-08
CVE-2025-55136 Emotion Recognition in Coversation 代码问题漏洞 — ERC 5.7 Medium2025-08-07
CVE-2025-54640 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.5 Medium2025-08-06
CVE-2025-54639 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.5 Medium2025-08-06
CVE-2025-54638 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.5 Medium2025-08-06
CVE-2025-54620 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.5 Medium2025-08-06
CVE-2025-53078 SAMSUNG DMS 安全漏洞 — Data Management Server 8.0 High2025-07-29
CVE-2025-8266 yanyutao0402 ChanCMS collect.js getArticle deserialization — ChanCMS 6.3 Medium2025-07-28
CVE-2025-8227 yanyutao0402 ChanCMS getArticle deserialization — ChanCMS 6.3 Medium2025-07-27
CVE-2025-54366 FreeScout's deserialization of untrusted data leads to Remote Code Execution — freescout 8.8 -2025-07-26
CVE-2025-26397 SolarWinds Observability Self-Hosted Deserialization of Untrusted Data Local Privilege Escalation Vulnerability — SolarWinds Observability Self-Hosted 7.8 High2025-07-24
CVE-2025-4393 Medtronic MyCareLink Patient Monitor Deserialization Vulnerability — MyCareLink Patient Monitor 24950 6.5 Medium2025-07-24
CVE-2016-15044 Kaltura < 11.1.0-2 PHP Object Injection RCE — Video Platform 9.8 -2025-07-23
CVE-2025-43489 Poly Clariti Manager - Multiple Security Vulnerabilities — Poly Clariti Manager 9.8 -2025-07-22
CVE-2025-7916 Simopro Technology|WinMatrix3 - Insecure Deserialization — WinMatrix3 9.8 Critical2025-07-21

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