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-20253 Cisco Unified Communications Products 安全漏洞 — Cisco Unified Contact Center Enterprise 9.9 Critical 2024-01-26
CVE-2024-0936 van_der_Schaar LAB TemporAI PKL File load_from_file deserialization — TemporAI 6.3 Medium 2024-01-26
CVE-2023-50943 Apache Airflow: Potential pickle deserialization vulnerability in XComs — Apache Airflow 8.2 - 2024-01-24
CVE-2024-22284 WordPress Asgaros Forum Plugin <= 2.7.2 is vulnerable to PHP Object Injection — Asgaros Forum 8.7 High 2024-01-24
CVE-2024-22309 WordPress ChatBot Plugin <= 5.1.0 is vulnerable to PHP Object Injection — ChatBot with AI 8.7 High 2024-01-24
CVE-2024-23636 SOFARPC Remote Command Execution(RCE) Vulnerbility — sofa-rpc 9.8 Critical 2024-01-23
CVE-2024-0739 Hecheng Leadshop leadshop.php deserialization — Leadshop 7.3 High 2024-01-19
CVE-2022-45845 WordPress Smart Slider 3 Plugin <= 3.5.1.9 is vulnerable to PHP Object Injection — Smart Slider 3 4.3 Medium 2024-01-19
CVE-2022-45083 WordPress ProfilePress Plugin <= 4.3.2 is vulnerable to PHP Object Injection — Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress 6.6 Medium 2024-01-19
CVE-2024-0654 DeepFaceLab Util.py deserialization — DeepFaceLab 5.3 Medium 2024-01-18
CVE-2024-0603 ZhiCms giftcontroller.php deserialization — ZhiCms 7.3 High 2024-01-16
CVE-2023-7032 Schneider Electric Easergy Studio 代码问题漏洞 — Easergy Studio 7.8 High 2024-01-09
CVE-2024-21318 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High 2024-01-09
CVE-2023-52202 WordPress HTML5 MP3 Player with Folder Feedburner Plugin <= 2.8.0 is vulnerable to PHP Object Injection — HTML5 MP3 Player with Folder Feedburner Playlist Free 9.1 Critical 2024-01-08
CVE-2023-52206 WordPress Page Builder: Live Composer Plugin <= 1.5.25 is vulnerable to PHP Object Injection — Page Builder: Live Composer 7.7 High 2024-01-08
CVE-2023-52205 WordPress HTML5 SoundCloud Player Plugin <= 2.8.0 is vulnerable to PHP Object Injection — HTML5 SoundCloud Player with Playlist Free 9.1 Critical 2024-01-08
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 Critical 2024-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 Critical 2024-01-08
CVE-2023-52219 WordPress Gecka Terms Thumbnails Plugin <= 1.1 is vulnerable to PHP Object Injection — Gecka Terms Thumbnails 9.9 Critical 2024-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 Critical 2024-01-08
CVE-2024-0302 fhs-opensource iparking vueLogin deserialization — iparking 6.3 Medium 2024-01-08
CVE-2023-51785 Apache InLong: Arbitrary File Read Vulnerability in Apache InLong Manager — Apache InLong 7.5AI High AI 2024-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 Critical 2023-12-31
CVE-2023-52181 WordPress Theme per user Plugin <= 1.0.1 is vulnerable to PHP Object Injection — Theme per user 10.0 Critical 2023-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 Critical 2023-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 Critical 2023-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 Critical 2023-12-29
CVE-2023-51470 WordPress Rencontre – Dating Site Plugin <= 3.11.1 is vulnerable to PHP Object Injection — Rencontre – Dating Site 9.9 Critical 2023-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 Critical 2023-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 High 2023-12-28

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