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-2023-52207 WordPress HTML5 MP3 Player with Playlist Free Plugin <= 3.0.0 is vulnerable to PHP Object Injection — HTML5 MP3 Player with Playlist Free 9.1 Critical2024-01-08
CVE-2023-52218 WordPress WooCommerce Tranzila Gateway Plugin <= 1.0.8 is vulnerable to PHP Object Injection — Woocommerce Tranzila Payment Gateway 10.0 Critical2024-01-08
CVE-2023-52219 WordPress Gecka Terms Thumbnails Plugin <= 1.1 is vulnerable to PHP Object Injection — Gecka Terms Thumbnails 9.9 Critical2024-01-08
CVE-2023-52225 WordPress Taggbox Plugin <= 3.1 is vulnerable to PHP Object Injection — Tagbox – UGC Galleries, Social Media Widgets, User Reviews & Analytics 10.0 Critical2024-01-08
CVE-2024-0302 fhs-opensource iparking vueLogin deserialization — iparking 6.3 Medium2024-01-08
CVE-2023-51785 Apache InLong: Arbitrary File Read Vulnerability in Apache InLong Manager — Apache InLong 7.5AIHighAI2024-01-03
CVE-2023-49777 WordPress YITH WooCommerce Product Add-Ons Plugin <= 4.3.0 is vulnerable to PHP Object Injection — YITH WooCommerce Product Add-Ons 9.1 Critical2023-12-31
CVE-2023-52181 WordPress Theme per user Plugin <= 1.0.1 is vulnerable to PHP Object Injection — Theme per user 10.0 Critical2023-12-31
CVE-2023-52182 WordPress ARI Stream Quiz Plugin <= 1.3.0 is vulnerable to PHP Object Injection — ARI Stream Quiz – WordPress Quizzes Builder 9.9 Critical2023-12-31
CVE-2023-51414 WordPress EnvíaloSimple Plugin <= 2.1 is vulnerable to PHP Object Injection — EnvíaloSimple: Email Marketing y Newsletters 9.6 Critical2023-12-29
CVE-2023-51422 WordPress WebinarIgnition Plugin <= 3.05.0 is vulnerable to PHP Object Injection — Webinar Plugin: Create live/evergreen/automated/instant webinars, stream & Zoom Meetings | WebinarIgnition 9.9 Critical2023-12-29
CVE-2023-51470 WordPress Rencontre – Dating Site Plugin <= 3.11.1 is vulnerable to PHP Object Injection — Rencontre – Dating Site 9.9 Critical2023-12-29
CVE-2023-51505 WordPress Active Products Tables for WooCommerce Plugin <= 1.0.6 is vulnerable to PHP Object Injection — Active Products Tables for WooCommerce. Professional products tables for WooCommerce store 10.0 Critical2023-12-29
CVE-2023-32513 WordPress GiveWP Plugin <= 2.25.3 is vulnerable to PHP Object Injection — GiveWP – Donation Plugin and Fundraising Platform 7.5 High2023-12-28
CVE-2023-32795 WordPress WooCommerce Product Add-ons Plugin <= 6.1.3 is vulnerable to PHP Object Injection — Product Add-Ons 8.2 High2023-12-28
CVE-2023-36381 WordPress Zippy Plugin <= 1.6.5 is vulnerable to PHP Object Injection — Zippy 6.6 Medium2023-12-28
CVE-2023-51700 WP-Mobile-BankID-Integration WordPress Database Deserialization: Potential for Object Injection — WP-Mobile-BankID-Integration 6.4 Medium2023-12-27
CVE-2023-32242 WordPress Woodmart Core Plugin <= 1.0.36 is vulnerable to PHP Object Injection — WoodMart - Multipurpose WooCommerce Theme 9.8 Critical2023-12-21
CVE-2023-49778 WordPress Sayfa Sayaç Plugin <= 2.6 is vulnerable to PHP Object Injection — Sayfa Sayac 10.0 Critical2023-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 High2023-12-21
CVE-2023-51656 Apache IoTDB: Unsafe deserialize map in Sync Tool — Apache IoTDB 9.8AICriticalAI2023-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 Medium2023-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 Critical2023-12-20
CVE-2023-49772 WordPress Genesis Simple Love Plugin <= 2.0 is vulnerable to PHP Object Injection — Genesis Simple Love 10.0 Critical2023-12-20
CVE-2023-28782 WordPress Gravity Forms Plugin <= 2.7.3 is vulnerable to PHP Object Injection — Gravity Forms 8.3 High2023-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 High2023-12-20
CVE-2023-46147 WordPress Themify Ultra Theme <= 7.3.5 is vulnerable to PHP Object Injection — Themify Ultra 7.4 High2023-12-20
CVE-2023-47507 WordPress Master Slider Pro Plugin <= 3.6.5 is vulnerable to PHP Object Injection — Master Slider Pro 7.1 High2023-12-20
CVE-2023-34027 WordPress Recently Viewed Products Plugin <= 1.0.0 is vulnerable to PHP Object Injection — Recently Viewed Products 8.3 High2023-12-19

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