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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

1761 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-2018-6331 Buck 安全漏洞 — Buck 9.8 -2018-12-31
CVE-2018-15381 Cisco Unity Express Arbitrary Command Execution Vulnerability — Cisco Unity Express 9.8 -2018-11-08
CVE-2018-15616 System Platform Web UI Deserialization — Avaya Aura® System Platform 9.8 -2018-10-17
CVE-2018-10911 Red Hat glusterfs服务器代码问题漏洞 — glusterfs: 5.5 -2018-09-04
CVE-2016-8648 Red Hat JBoss Fuse和JBoss A-MQ 安全漏洞 — Karaf 7.2 -2018-08-01
CVE-2016-8653 RedHat Jboss Fuse和Jboss A-MQ 安全漏洞 — Fuse 5.3 -2018-08-01
CVE-2016-9483 PHP FormMail Generator generates PHP code for standard web forms, and the code generated is vulnerable to unsafe deserialization of untrusted data — Generator 9.8 -2018-07-13
CVE-2016-9498 ManageEngine Applications Manager 12 and 13, allows unserialization of unsafe Java objects — Applications Manager 9.8 -2018-07-13
CVE-2017-3199 GraniteDS, version 3.1.1.GA, Action Message Format (AMF3) Java implementation is vulnerable to insecure deserialization — Framework 8.1 -2018-06-11
CVE-2017-3201 Flamingo amf-serializer by Exadel, version 2.2.0, Action Message Format (AMF3) Java implementation is vulnerable to insecure deserialization — Flamingo amf-serializer 8.1 -2018-06-11
CVE-2017-3203 Pivotal/Spring Spring-flex's Action Message Format (AMF3) Java implementation is vulnerable to insecure deserialization — Spring-flex 8.1 -2018-06-11
CVE-2017-3207 WebORB for Java by Midnight Coders, version 5.1.1.0, Action Message Format (AMF3) Java implementation is vulnerable to insecure deserialization — WebORB for Java 8.1 -2018-06-11
CVE-2017-2608 CloudBees Jenkins 安全漏洞 — jenkins 9.8 -2018-05-15
CVE-2018-7529 OSIsoft PI Data Archive 安全漏洞 — OSIsoft PI Data Archive 7.5 -2018-03-14
CVE-2016-9585 Red Hat JBoss Enterprise Application Platform 安全漏洞 — EAP-5 7.5 -2018-03-09
CVE-2017-15089 Infinispan Hotrod客户端安全漏洞 — infinispan 8.8 -2018-02-15
CVE-2017-17406 Netgain Enterprise Manager 安全漏洞 — NetGain Systems Enterprise Manager 9.8 -2018-01-23
CVE-2017-0903 RubyGems 安全漏洞 — RubyGems 9.8 -2017-10-11
CVE-2017-12149 Red Hat JBoss Enterprise Application Platform Jboss Application Server 安全漏洞 — jbossas 9.8 -2017-10-04
CVE-2017-11153 Synology Photo Station 安全漏洞 — Synology Photo Station 9.8 -2017-08-08
CVE-2017-7504 Red Hat Jboss Application Server 安全漏洞 — JBoss 9.8 -2017-05-19

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