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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

2494 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)
Integrity Modify 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.
Availability DoS: 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.
Other Varies 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, Implementation If 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.
Implementation When 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.
Implementation Explicitly define a final object() to prevent deserialization.
Architecture and Design, Implementation Make 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.
Implementation Avoid 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 ID Title CVSS Severity Published
CVE-2024-38094 Microsoft SharePoint Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 7.2 High 2024-07-09
CVE-2024-38023 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 7.2 High 2024-07-09
CVE-2024-38024 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 7.2 High 2024-07-09
CVE-2023-32737 Siemens SIMATIC STEP 代码问题漏洞 — SIMATIC STEP 7 Safety V18 6.3 Medium 2024-07-09
CVE-2023-32735 Siemens SIMATIC WinCC和SIMATIC STEP 代码问题漏洞 — SIMATIC STEP 7 Safety V16 6.5 Medium 2024-07-09
CVE-2022-45147 Siemens SIMATIC PCS和SIMATIC STEP 代码问题漏洞 — SIMATIC PCS neo V4.0 7.8 High 2024-07-09
CVE-2024-37502 WordPress Social Login plugin <= 2.6.3 - PHP Object Injection vulnerability — WooCommerce Social Login 5.4 Medium 2024-07-09
CVE-2024-6525 D-Link DAR-7000 decodmail.php deserialization — DAR-7000 2.7 Low 2024-07-05
CVE-2024-6441 ORIPA LoaderXML.java deserialization — ORIPA 6.3 Medium 2024-07-02
CVE-2024-36984 Remote Code Execution through Serialized Session Payload in Splunk Enterprise on Windows — Splunk Enterprise 8.8 High 2024-07-01
CVE-2024-29040 Fapi Verify Quote: Does not detect if quote was not generated by TPM — tpm2-tss 4.3 Medium 2024-06-28
CVE-2024-5016 WhatsUp Gold OnMessage Deserialization of Untrusted Data Remote Code Execution Vulnerability — WhatsUp Gold 7.2 High 2024-06-25
CVE-2024-35780 WordPress Page Builder: Live Composer plugin <= 1.5.42 - Contributor+ PHP Object Injection vulnerability — Page Builder: Live Composer 8.5 High 2024-06-19
CVE-2024-5649 Universal Slider <= 1.6.5 - Authenticated (Contributor+) PHP Object Injection — Universal Slider 5.4 Medium 2024-06-19
CVE-2024-5724 Photo Video Gallery Master <= 1.5.3 - Authenticated (Contributor+) PHP Object Injection — Photo Video Gallery Master 8.8 High 2024-06-19
CVE-2024-5871 WooCommerce - Social Login <= 2.6.2 - Unauthenticated PHP Object Injection — WooCommerce - Social Login 9.8 Critical 2024-06-15
CVE-2024-5671 Trellix IPS Manager 代码问题漏洞 — Intrusion Prevention System (IPS) Manager 9.8 Critical 2024-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 Critical 2024-06-13
CVE-2024-3468 Deserialization of Untrusted Data in AVEVA PI Web API — PI Web API 8.8AI High AI 2024-06-12
CVE-2024-3467 Deserialization of Untrusted Data in AVEVA PI Asset Framework Client — PI Asset Framework Client 8.8AI High AI 2024-06-12
CVE-2024-28964 Dell Common Event Enabler 代码问题漏洞 — Common Event Enabler 7.8 High 2024-06-12
CVE-2024-35249 Microsoft Dynamics 365 Business Central Remote Code Execution Vulnerability — Microsoft Dynamics 365 Business Central 2023 Release Wave 1 8.8 High 2024-06-11
CVE-2024-5675 Unreliable data deserialization vulnerability in Mentor — Mentor – Employee Portal 10.0 Critical 2024-06-06
CVE-2024-37065 Skops 安全漏洞 — Skops 7.8 High 2024-06-04
CVE-2024-37064 ydata-profiling 安全漏洞 — ydata-profiling 7.8 High 2024-06-04
CVE-2024-37062 ydata-profiling 安全漏洞 — ydata-profiling 7.8 High 2024-06-04
CVE-2024-37060 MLflow 安全漏洞 — MLflow 8.8 High 2024-06-04
CVE-2024-37059 Mlflow 安全漏洞 — MLflow 8.8 High 2024-06-04
CVE-2024-37058 MLflow 安全漏洞 — MLflow 8.8 High 2024-06-04
CVE-2024-37057 MLflow 安全漏洞 — MLflow 8.8 High 2024-06-04

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