Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-502 (可信数据的反序列化) — Vulnerability Class 1687

1687 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-2022-39298 Deserialization of untrusted data in MelisFront — melis-front 7.7 High2022-10-12
CVE-2022-39256 Orckestra C1 CMS's deserialization of untrusted data allows for arbitrary code execution. — C1-CMS-Foundation 9.0 Critical2022-09-27
CVE-2022-2903 NinjaForms < 3.6.13 - Admin+ PHP Objection Injection — Ninja Forms Contact Form – The Drag and Drop Form Builder for WordPress 7.2 -2022-09-26
CVE-2022-40955 Deserialization attack in Apache InLong prior to version 1.3.0 allows RCE via JDBC — Apache InLong 8.8 -2022-09-20
CVE-2022-36038 CircuitVerse potential RCE vulnerability via Oj.load — CircuitVerse 8.8 High2022-09-06
CVE-2022-2434 String Locator <= 2.5.0 - Cross-Site Request Forgery to PHAR Deserialization — String locator 8.8 High2022-09-06
CVE-2022-2436 Download Manager <= 3.2.49 - Authenticated (Contributor+) PHAR Deserialization — Download Manager 8.8 High2022-09-06
CVE-2022-2438 Broken Link Checker <= 1.11.16 - Authenticated (Admin+) PHAR Deserialization — Broken Link Checker 7.2 High2022-09-06
CVE-2022-2442 Migration, Backup, Staging – WPvivid <= 0.9.74 - Authenticated (Admin+) PHAR Deserialization — WPvivid — Backup, Migration & Staging 7.2 High2022-09-06
CVE-2022-2433 WordPress Infinite Scroll – Ajax Load More <= 5.5.3 - Cross-Site Request Forgery to PHAR Deserialization — Ajax Load More – Infinite Scroll, Load More, & Lazy Load 7.5 High2022-09-06
CVE-2022-2830 Deserialization of Untrusted Data in GravityZone Console On-Premise (VA-10573) — GravityZone Console On-Premise 8.8 High2022-09-05
CVE-2022-29063 Java Deserialization via RMI Connection from the Solr plugin of Apache OFBiz — Apache OFBiz 9.8 -2022-09-02
CVE-2022-37023 Apache Geode deserialization of untrusted data flaw when using REST API on Java 8 or Java 11 — Apache Geode 8.8 -2022-08-31
CVE-2022-37022 Apache Geode deserialization of untrusted data flaw when using JMX over RMI on Java 11 — Apache Geode 9.8 -2022-08-31
CVE-2022-37021 Apache Geode deserialization of untrusted data flaw when using JMX over RMI on Java 8. — Apache Geode 9.8 -2022-08-31
CVE-2022-34668 NVIDIA NVFLARE 代码问题漏洞 — NVIDIA FLARE 9.8 Critical2022-08-29
CVE-2022-2465 ISaGRAF Workbench Deserialization of Untrusted Data CWE-502 — ISaGRAF Workbench 8.6 High2022-08-25
CVE-2021-25642 Apache Hadoop YARN remote code execution in ZKConfigurationStore of capacity scheduler — Apache Hadoop 8.8 -2022-08-25
CVE-2021-4178 Kubernetes 代码问题漏洞 — kubernetes-client 6.7 -2022-08-24
CVE-2022-2886 Laravel deserialization — Laravel 5.0 Medium2022-08-19
CVE-2022-2870 laravel deserialization — laravel 4.1 Medium2022-08-17
CVE-2022-36006 Authenticated remote code execution due to insecure deserialization (GHSL-2022-063) — arvados 7.9 High2022-08-14
CVE-2022-33947 BIG-IP DNS TMUI Vulnerability CVE-2022-33947 — BIG-IP DNS 5.4 Medium2022-08-04
CVE-2022-28684 DevExpress 代码问题漏洞 — DevExpress 8.8 -2022-08-03
CVE-2022-35223 EasyUse MailHunter Ultimate - Deserialization of Untrusted Data — MailHunter Ultimate 9.8 Critical2022-08-02
CVE-2022-35872 Inductive Automation Ignition 代码问题漏洞 — Ignition 7.8 -2022-07-25
CVE-2022-35870 Inductive Automation Ignition 代码问题漏洞 — Ignition 8.4 -2022-07-25
CVE-2022-33318 Mitsubishi Electric MC Works64 代码问题漏洞 — GENESIS64 9.8 Critical2022-07-20
CVE-2022-33320 Mitsubishi Electric MC Works64 代码问题漏洞 — GENESIS64 7.8 High2022-07-20
CVE-2022-33315 Mitsubishi Electric MC Works64和ICONICS GENESIS64 代码问题漏洞 — GENESIS64 7.8 High2022-07-20

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