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-1859 Slider Responsive Slideshow – Image slider, Gallery slideshow <= 1.3.8 - Authenticated (Contributor+) PHP Object Injection — Responsive Slideshow 8.8 High 2024-03-01
CVE-2023-51518 Apache James server: Privilege escalation via JMX pre-authentication deserialisation — Apache James server 7.8 - 2024-02-27
CVE-2024-1750 TemmokuMVC Image Download images_get_down.php img_replace deserialization — TemmokuMVC 5.6 Medium 2024-02-22
CVE-2024-1748 van_der_Schaar LAB AutoPrognosis Release Note load_model_from_file deserialization — AutoPrognosis 5.0 Medium 2024-02-22
CVE-2023-51389 HertzBeat SnakeYAML Deser RCE — hertzbeat 9.8 Critical 2024-02-22
CVE-2024-23114 Apache Camel: Camel-CassandraQL: Unsafe Deserialization from CassandraAggregationRepository — Apache Camel 9.8 - 2024-02-20
CVE-2024-22369 Apache Camel: Camel-SQL: Unsafe Deserialization from JDBCAggregationRepository — Apache Camel 9.8 - 2024-02-20
CVE-2024-1651 Torrentpier 2.4.1 - RCE — Torrentpier 10.0 Critical 2024-02-19
CVE-2023-40057 SolarWinds Access Rights Manager (ARM) Deserialization of Untrusted Data Remote Code Execution — Access Rights Manager 9.0 Critical 2024-02-15
CVE-2024-23478 SolarWinds Access Rights Manager (ARM) Deserialization of Untrusted Data Remote Code Execution — Access Rights Manager 8.0 High 2024-02-15
CVE-2023-46615 WordPress KD Coming Soon Plugin <= 1.7 is vulnerable to PHP Object Injection — KD Coming Soon 5.4 Medium 2024-02-12
CVE-2024-23512 WordPress ProductX – Gutenberg WooCommerce Blocks Plugin <= 3.1.4 is vulnerable to PHP Object Injection — ProductX – WooCommerce Builder & Gutenberg WooCommerce Blocks 8.7 High 2024-02-12
CVE-2024-23513 WordPress PropertyHive Plugin <= 2.0.5 is vulnerable to PHP Object Injection — PropertyHive 8.7 High 2024-02-12
CVE-2024-24796 WordPress Event Manager for WooCommerce Plugin <= 4.1.1 is vulnerable to PHP Object Injection — Event Manager and Tickets Selling Plugin for WooCommerce – WpEvently – WordPress Plugin 8.2 High 2024-02-12
CVE-2024-24797 WordPress ERE Recently Viewed Plugin <= 1.3 is vulnerable to PHP Object Injection — ERE Recently Viewed – Essential Real Estate Add-On 9.8 Critical 2024-02-12
CVE-2024-24926 WordPress Brooklyn Theme <= 4.9.7.6 is vulnerable to PHP Object Injection — Brooklyn | Creative Multi-Purpose Responsive WordPress Theme 7.5 High 2024-02-12
CVE-2024-25100 WordPress Coupon Referral Program plugin < 1.8.4 - Unauthenticated PHP Object Injection vulnerability — Coupon Referral Program 10.0 Critical 2024-02-12
CVE-2024-1432 DeepFaceLab main.py apply_xseg deserialization — DeepFaceLab 5.0 Medium 2024-02-11
CVE-2024-1353 PHPEMS index.api.php index deserialization — PHPEMS 6.3 Medium 2024-02-09
CVE-2024-24590 Allegro 代码问题漏洞 — ClearML 8.0 High 2024-02-06
CVE-2024-0668 Advanced Database Cleaner <= 3.1.3 - Authenticated(Administrator+) PHP Object Injection via process_bulk_action — Advanced Database Cleaner – Optimize & Clean Database to Speed Up Site Performance 6.6 Medium 2024-02-05
CVE-2023-6933 Better Search Replace <= 1.4.4 - Unauthenticated PHP Object Injection — Better Search Replace 8.8 High 2024-02-05
CVE-2024-1225 QiboSoft QiboCMS X1 Pay.php rmb_pay deserialization — QiboCMS X1 7.3 High 2024-02-05
CVE-2024-1198 openBI Phar User.php addxinzhi deserialization — openBI 6.3 Medium 2024-02-02
CVE-2024-22320 IBM Operational Decision Manager code execution — Operational Decision Manager 9.8 Critical 2024-02-02
CVE-2024-23328 The Dataease datasource exists deserialization and arbitrary file read vulnerability — dataease 9.1 Critical 2024-02-01
CVE-2024-1032 openBI Test Connection Databasesource.php testConnection deserialization — openBI 7.3 High 2024-01-30
CVE-2024-0960 flink-extended ai-flow workflow_command.py cloudpickle.loads deserialization — ai-flow 5.0 Medium 2024-01-27
CVE-2024-0959 StanfordVL GibsonEnv pposgd_fuse.py cloudpickle.load deserialization — GibsonEnv 5.0 Medium 2024-01-27
CVE-2024-0937 van_der_Schaar LAB synthcity PKL File load_from_file deserialization — synthcity 6.3 Medium 2024-01-26

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