Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-502 (可信数据的反序列化) — Vulnerability Class 1698

1698 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-5671 Trellix IPS Manager 代码问题漏洞 — Intrusion Prevention System (IPS) Manager 9.8 Critical2024-06-14
CVE-2024-4371 CoDesigner WooCommerce Builder for Elementor – Customize Checkout, Shop, Email, Products & More <= 4.4.1 - Unauthenticated PHP Object Injection — CoDesigner – All in One Elementor WooCommerce Builder 9.0 Critical2024-06-13
CVE-2024-3468 Deserialization of Untrusted Data in AVEVA PI Web API — PI Web API 8.8AIHighAI2024-06-12
CVE-2024-3467 Deserialization of Untrusted Data in AVEVA PI Asset Framework Client — PI Asset Framework Client 8.8AIHighAI2024-06-12
CVE-2024-28964 Dell Common Event Enabler 代码问题漏洞 — Common Event Enabler 7.8 High2024-06-12
CVE-2024-35249 Microsoft Dynamics 365 Business Central Remote Code Execution Vulnerability — Microsoft Dynamics 365 Business Central 2024 Release Wave 1 8.8 High2024-06-11
CVE-2024-5675 Unreliable data deserialization vulnerability in Mentor — Mentor – Employee Portal 10.0 Critical2024-06-06
CVE-2024-37065 Skops 安全漏洞 — Skops 7.8 High2024-06-04
CVE-2024-37064 ydata-profiling 安全漏洞 — ydata-profiling 7.8 High2024-06-04
CVE-2024-37062 ydata-profiling 安全漏洞 — ydata-profiling 7.8 High2024-06-04
CVE-2024-37060 MLflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-37059 Mlflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-37058 MLflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-37057 MLflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-37056 MLflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-37055 MLflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-37054 MLflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-37053 Mlflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-37052 Mlflow 安全漏洞 — MLflow 8.8 High2024-06-04
CVE-2024-3300 Pre-authentication Unsafe .NET object deserialization vulnerability affecting DELMIA Apriso Release 2019 through Release 2024 — DELMIA Apriso 9.0 Critical2024-05-30
CVE-2024-3301 Post-authentication Unsafe .NET object deserialization vulnerability affecting DELMIA Apriso Release 2019 through Release 2024 — DELMIA Apriso 8.5 High2024-05-30
CVE-2024-26289 Remote Code Inclusion Vulnerability in Multiple PMB Versions — PMB 9.8 Critical2024-05-27
CVE-2024-5352 anji-plus AJ-Report validationRules deserialization — AJ-Report 6.3 Medium2024-05-26
CVE-2024-5351 anji-plus AJ-Report Javascript getValueFromJs deserialization — AJ-Report 6.3 Medium2024-05-26
CVE-2024-5085 Hash Form – Drag & Drop Form Builder <= 1.1.0 - Unauthenticated PHP Object Injection — Hash Form – Drag & Drop Form Builder 8.1 High2024-05-23
CVE-2024-4471 140+ Widgets | Best Addons For Elementor – FREE <= 1.4.3.1 - Authenticated (Contributor+) PHP Object Injection — Xpro Addons — 140+ Widgets for Elementor 8.0 High2024-05-23
CVE-2024-4157 Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag & Drop WP Form Builder <= 5.1.15 - PHP Object Injection via extractDynamicValues — Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder 7.5 High2024-05-22
CVE-2024-31879 IBM i denial of service — i 7.5 High2024-05-18
CVE-2024-4733 ShiftController Employee Shift Scheduling <= 4.9.57 - Authenticated (Contributor+) PHP Object Injection — ShiftController Employee Shift Scheduling 7.5 High2024-05-16
CVE-2024-34751 WordPress Order Export & Order Import for WooCommerce plugin <= 2.4.9 - PHP Object Injection vulnerability — Order Export & Order Import for WooCommerce 4.4 Medium2024-05-16

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