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-2023-32795 WordPress WooCommerce Product Add-ons Plugin <= 6.1.3 is vulnerable to PHP Object Injection — Product Add-Ons 8.2 High 2023-12-28
CVE-2023-36381 WordPress Zippy Plugin <= 1.6.5 is vulnerable to PHP Object Injection — Zippy 6.6 Medium 2023-12-28
CVE-2023-51700 WP-Mobile-BankID-Integration WordPress Database Deserialization: Potential for Object Injection — WP-Mobile-BankID-Integration 6.4 Medium 2023-12-27
CVE-2023-32242 WordPress Woodmart Core Plugin <= 1.0.36 is vulnerable to PHP Object Injection — WoodMart - Multipurpose WooCommerce Theme 9.8 Critical 2023-12-21
CVE-2023-49778 WordPress Sayfa Sayaç Plugin <= 2.6 is vulnerable to PHP Object Injection — Sayfa Sayac 10.0 Critical 2023-12-21
CVE-2023-49826 WordPress Soledad Theme <= 8.4.1 is vulnerable to PHP Object Injection — Soledad – Multipurpose, Newspaper, Blog & WooCommerce WordPress Theme 8.1 High 2023-12-21
CVE-2023-51656 Apache IoTDB: Unsafe deserialize map in Sync Tool — Apache IoTDB 9.8AI Critical AI 2023-12-21
CVE-2022-47599 WordPress File Manager Plugin <= 5.2.7 is vulnerable to PHP Object Injection — File Manager – 100% Free & Open Source File Manager Plugin for WordPress | Bit File Manager 5.5 Medium 2023-12-20
CVE-2023-7018 Deserialization of Untrusted Data in huggingface/transformers — huggingface/transformers 9.8 - 2023-12-20
CVE-2023-49773 WordPress BCorp Shortcodes Plugin <= 0.23 is vulnerable to PHP Object Injection — BCorp Shortcodes 10.0 Critical 2023-12-20
CVE-2023-49772 WordPress Genesis Simple Love Plugin <= 2.0 is vulnerable to PHP Object Injection — Genesis Simple Love 10.0 Critical 2023-12-20
CVE-2023-28782 WordPress Gravity Forms Plugin <= 2.7.3 is vulnerable to PHP Object Injection — Gravity Forms 8.3 High 2023-12-20
CVE-2023-40555 WordPress Flatsome Theme <= 3.17.5 is vulnerable to PHP Object Injection — Flatsome | Multi-Purpose Responsive WooCommerce Theme 8.3 High 2023-12-20
CVE-2023-46147 WordPress Themify Ultra Theme <= 7.3.5 is vulnerable to PHP Object Injection — Themify Ultra 7.4 High 2023-12-20
CVE-2023-47507 WordPress Master Slider Pro Plugin <= 3.6.5 is vulnerable to PHP Object Injection — Master Slider Pro 7.1 High 2023-12-20
CVE-2023-34027 WordPress Recently Viewed Products Plugin <= 1.0.0 is vulnerable to PHP Object Injection — Recently Viewed Products 8.3 High 2023-12-19
CVE-2023-34382 WordPress Dokan Plugin <= 3.7.19 is vulnerable to PHP Object Injection — Dokan – Best WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy 4.4 Medium 2023-12-19
CVE-2023-37390 WordPress Themesflat Addons For Elementor Plugin <= 2.0.0 is vulnerable to PHP Object Injection — Themesflat Addons For Elementor 8.3 High 2023-12-19
CVE-2023-6730 Deserialization of Untrusted Data in huggingface/transformers — huggingface/transformers 9.8 - 2023-12-19
CVE-2023-46154 WordPress e2pdf Plugin <= 1.20.18 is vulnerable to PHP Object Injection — E2Pdf – Export To Pdf Tool for WordPress 6.6 Medium 2023-12-18
CVE-2023-49819 WordPress Structured Content Plugin <= 1.5.3 is vulnerable to PHP Object Injection — Structured Content (JSON-LD) #wpsc 7.5 High 2023-12-18
CVE-2023-46279 Apache Dubbo: Bypass deny serialize list check in Apache Dubbo — Apache Dubbo 9.8 - 2023-12-15
CVE-2023-29234 Bypass serialize checks in Apache Dubbo — Apache Dubbo 9.8 - 2023-12-15
CVE-2023-6656 DeepFaceLab DFLJPG.py deserialization — DeepFaceLab 5.0 Medium 2023-12-10
CVE-2023-6654 PHPEMS Session Data session.cls.php deserialization — PHPEMS 6.3 Medium 2023-12-10
CVE-2023-6580 D-Link DIR-846 QoS POST deserialization — DIR-846 8.8 High 2023-12-07
CVE-2023-49297 Unsafe YAML deserialization in PyDrive2 — PyDrive2 3.3 Low 2023-12-05
CVE-2023-46674 Elasticsearch-hadoop Unsafe Deserialization — Elasticsearch-Hadoop 6.0 Medium 2023-12-05
CVE-2023-47207 Delta Electronics InfraSuite Device Master Deserialization of Untrusted Data — InfraSuite Device Master 9.8 Critical 2023-11-30
CVE-2023-46302 Apache Submarine: Fix CVE-2022-1471 SnakeYaml unsafe deserialization — Apache Submarine 9.8AI Critical AI 2023-11-20

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