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-2024-4838 ConvertPlus <= 3.5.26 - Authenticated (Contributor+) PHP Object Injection — ConvertPlus 7.5 High2024-05-16
CVE-2024-4200 Progress Telerik Reporting Local Deserialization Vulnerability — Telerik Reporting 7.7 High2024-05-15
CVE-2024-3483 Remote Code Execution vulnerability in the iManager — iManager 7.8 High2024-05-15
CVE-2024-3967 Remote Code Execution vulnerability in the iManager — iManager 7.6 High2024-05-15
CVE-2024-30042 Microsoft Excel Remote Code Execution Vulnerability — Office Online Server 7.8 High2024-05-14
CVE-2024-30044 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 7.2 High2024-05-14
CVE-2024-4413 Hotel Booking Lite <= 4.11.1 - Unauthenticated PHP Object Injection — MotoPress Hotel Booking 9.8 Critical2024-05-10
CVE-2023-38264 IBM SDK, Java Technology Edition denial of service — SDK, Java Technology Edition 5.9 Medium2024-05-10
CVE-2024-4044 Deserialization of Untrusted Data Vulnerability in FlexLogger and InstrumentStudio — FlexLogger 7.8 High2024-05-10
CVE-2024-4699 D-Link DAR-8000-10 importhtml.php deserialization — DAR-8000-10 6.3 Medium2024-05-10
CVE-2024-2290 Advanced Ads – Ad Manager & AdSense <= 1.52.1 - Authenticated (Admin+) PHP Object Injection — Advanced Ads – Ad Manager & AdSense 7.2 High2024-05-09
CVE-2024-3070 Last Viewed Posts by WPBeginner <= 1.0.0 - Unauthenticated PHP Object Injection — Last Viewed Posts by WPBeginner 9.8 Critical2024-05-09
CVE-2024-3954 Ditty – Responsive News Tickers, Sliders, and Lists <= 3.1.38 - Authenticated (Contributor+) PHP Object Injection — Ditty – Responsive News Tickers, Sliders, and Lists 8.8 High2024-05-09
CVE-2024-28075 SolarWinds ARM Deserialization of Untrusted Data Remote Code Execution — Access Rights Manager 9.0 Critical2024-05-09
CVE-2024-34433 WordPress One Click Demo Import plugin <=3.2.0 - PHP Object Injection vulnerability — One Click Demo Import 4.4 Medium2024-05-09
CVE-2024-4606 WordPress Ultimate Store Kit Elementor Addons, Woocommerce Builder, EDD Builder plugin <= 2.0.3 - PHP Object Injection vulnerability — Ultimate Store Kit Elementor Addons 5.4 Medium2024-05-09
CVE-2024-29800 WordPress Timber plugin <= 1.23.0 - Deserialization of untrusted data vulnerability — Timber 8.0 High2024-05-09
CVE-2024-22460 Dell DM5500 代码问题漏洞 — Data Manager Appliance Software (DMAS) 2.2 Low2024-05-08
CVE-2024-26579 Apache Inlong JDBC Vulnerability — Apache InLong 9.8AICriticalAI2024-05-08
CVE-2024-3240 ConvertPlug <= 3.5.25 - Authenticated (Contributor+) PHP Object Injection — ConvertPlus 8.8 High2024-05-04
CVE-2024-34075 kurwov vulnerable to Denial of Service due to improper data sanitization — kurwov 6.2 Medium2024-05-03
CVE-2024-34072 Deserialization of Untrusted Data in sagemaker-python-sdk — sagemaker-python-sdk 7.8 High2024-05-03
CVE-2023-51576 Voltronic Power ViewPower Deserialization of Untrusted Data Remote Code Execution Vulnerability — ViewPower 9.8 -2024-05-03
CVE-2023-50223 Inductive Automation Ignition ExtendedDocumentCodec Deserialization of Untrusted Data Remote Code Execution Vulnerability — Ignition 8.8 -2024-05-03
CVE-2023-50221 Inductive Automation Ignition ResponseParser SerializedResponse Deserialization of Untrusted Data Remote Code Execution Vulnerability — Ignition 8.8 -2024-05-03
CVE-2023-50222 Inductive Automation Ignition ResponseParser Notification Deserialization of Untrusted Data Remote Code Execution Vulnerability — Ignition 8.8 -2024-05-03
CVE-2023-50220 Inductive Automation Ignition Base64Element Deserialization of Untrusted Data Remote Code Execution Vulnerability — Ignition 8.8 -2024-05-03
CVE-2023-50219 Inductive Automation Ignition RunQuery Deserialization of Untrusted Data Remote Code Execution Vulnerability — Ignition 8.8 -2024-05-03
CVE-2023-50218 Inductive Automation Ignition ModuleInvoke Deserialization of Untrusted Data Remote Code Execution Vulnerability — Ignition 8.8 -2024-05-03
CVE-2023-39476 Inductive Automation Ignition JavaSerializationCodec Deserialization of Untrusted Data Remote Code Execution Vulnerability — Ignition 9.8 -2024-05-03

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