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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

2486 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-2020-10917 NEC ESMPRO Manager 代码问题漏洞 — ESMPRO Manager 9.8 - 2020-07-22
CVE-2020-12007 Mitsubishi Electric MC Works64和ICONICS GENESIS64 FrameWorX Server 代码问题漏洞 — MC Works64 9.8 - 2020-07-16
CVE-2020-12015 Mitsubishi Electric MC Works64和ICONICS GENESIS64 Platform Services 代码问题漏洞 — MC Works64 7.5 - 2020-07-16
CVE-2020-12009 Mitsubishi Electric MC Works64和ICONICS GENESIS64 Workbench Pack-and-Go 代码问题漏洞 — MC Works64 7.5 - 2020-07-16
CVE-2020-10740 Red Hat Wildfly 代码问题漏洞 — wildfly 6.6 Medium 2020-06-22
CVE-2020-8165 Ruby on Rails 代码问题漏洞 — https://github.com/rails/rails 9.8 - 2020-06-19
CVE-2020-8164 Ruby on Rails 代码问题漏洞 — https://github.com/rails/rails 7.5 - 2020-06-19
CVE-2020-5411 Jackson Configuration Allows Code Execution with Unknown "Serialization Gadgets" — Spring Batch 9.8 - 2020-06-11
CVE-2020-4043 Phar unserialization vulnerability in phpMussel — phpMussel 7.7 High 2020-06-10
CVE-2020-12000 Inductive Automation Ignition 代码问题漏洞 — Ignition 8 Gateway 7.5 - 2020-06-09
CVE-2020-10644 Inductive Automation Ignition 代码问题漏洞 — Ignition 8 Gateway 7.5 - 2020-06-09
CVE-2020-11067 Deserialization of Untrusted Data in TYPO3 CMS — TYPO3 CMS 8.8 High 2020-05-13
CVE-2020-10915 Veeam One Agent 代码问题漏洞 — One Agent 9.8 - 2020-04-22
CVE-2020-10914 Veeam One Agent 代码问题漏洞 — One Agent 9.8 - 2020-04-22
CVE-2020-6219 SAP Business Objects Business Intelligence Platform 代码问题漏洞 — SAP Business Objects Business Intelligence Platform (CrystalReports WebForm Viewer) 8.8 - 2020-04-14
CVE-2019-2391 JS-bson may incorrectly serialise some requests — js-bson 4.2 Medium 2020-03-31
CVE-2020-6967 Rockwell Automation FactoryTalk Diagnostics 代码问题漏洞 — Rockwell Automation All versions of FactoryTalk Diagnostics software, a subsystem of the FactoryTalk Services Platform 9.8 - 2020-03-23
CVE-2020-5327 Dell Security Management Server 代码问题漏洞 — Dell Encryption Enterprise 8.1 High 2020-03-06
CVE-2019-14893 FasterXML jackson-databind 代码问题漏洞 — jackson-databind 8.1 - 2020-03-02
CVE-2019-14892 FasterXML jackson-databind 代码问题漏洞 — jackson-databind 9.8 - 2020-03-02
CVE-2020-6770 Deserialization of Untrusted Data in Bosch BVMS Mobile Video Service — DIVAR IP 3000 10.0 Critical 2020-02-07
CVE-2020-6959 多款Honeywell产品 代码问题漏洞 — Honeywell Maxpro VMS & NVR 9.8 - 2020-01-22
CVE-2019-17635 Eclipse Memory Analyzer 代码问题漏洞 — Eclipse Memory Analyzer 7.8 - 2020-01-17
CVE-2019-17571 Apache Log4j 代码问题漏洞 — Log4j 8.1 - 2019-12-20
CVE-2019-18316 Siemens SPPA-T3000 代码问题漏洞 — SPPA-T3000 Application Server 9.8 - 2019-12-12
CVE-2019-18283 Siemens SPPA-T3000 代码问题漏洞 — SPPA-T3000 Application Server 9.8 - 2019-12-12
CVE-2019-19230 CA Release Automation DataManagement 安全漏洞 — CA Release Automation 9.8 Critical 2019-12-09
CVE-2019-18580 Dell EMC Storage Monitoring and Reporting 代码问题漏洞 — EMC Storage M&R 9.8 - 2019-11-26
CVE-2019-15271 Cisco Small Business RV016, RV042, RV042G, and RV082 Routers Arbitrary Command Execution Vulnerability — Cisco Small Business RV Series Router Firmware 8.8 - 2019-11-26
CVE-2019-10202 Red Hat JBoss Enterprise Application Platform 代码问题漏洞 — codehaus 9.8 - 2019-10-01

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