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-33316 Mitsubishi Electric MC Works64 和 ICONICS GENESIS64 代码问题漏洞 — GENESIS64 7.8 High2022-07-20
CVE-2022-27580 Safety 代码问题漏洞 — SICK Safety Designer 7.8 -2022-07-19
CVE-2022-27579 SICK Flexi Soft Designer 代码问题漏洞 — SICK Flexi Soft Designer 7.8 -2022-07-19
CVE-2022-1984 HYPR 代码问题漏洞 — HYPR Windows WFA 4.5 Medium2022-07-19
CVE-2022-24082 Pegasystem PEGA Platform 代码问题漏洞 — Pega Infinity 9.8 -2022-07-19
CVE-2022-2437 Feed Them Social – for Twitter feed, Youtube and more <= 2.9.8.5 - Unauthenticated PHAR Deserialization — Feed Them Social – Social Media Feeds, Video, and Photo Galleries 9.8 Critical2022-07-18
CVE-2022-2444 Visualizer: Tables and Charts Manager for WordPress <= 3.7.9 - Authenticated (Contributor+) PHAR Deserialization — Visualizer: Tables and Charts Manager for WordPress 8.8 High2022-07-18
CVE-2022-31605 NVIDIA NVFLARE 代码问题漏洞 — NVIDIA FLARE 9.8 Critical2022-07-01
CVE-2022-31604 NVIDIA NVFLARE 代码问题漏洞 — NVIDIA FLARE 9.8 Critical2022-07-01
CVE-2022-31115 Unsafe YAML deserialization in opensearch-ruby — opensearch-ruby 8.8 High2022-06-30
CVE-2022-29615 SAP NetWeaver Developer Studio 代码问题漏洞 — SAP NetWeaver Developer Studio (NWDS) 6.5 -2022-06-14
CVE-2022-29875 多款Siemens 产品代码问题漏洞 — Biograph Horizon PET/CT Systems 9.8 -2022-06-01
CVE-2022-1660 Keysight N6854A Geolocation server and N6841A RF Sensor software — N6854A Geolocation server and N6841A RF Sensor software 9.8 Critical2022-05-31
CVE-2021-32935 Cognex In-Sight OPC Server - Deserialization of Untrusted Data — In-Sight OPC Server 8.8 High2022-05-23
CVE-2022-1118 Rockwell Automation ISaGRAF Deserialization of Untrusted Data — Connected Component Workbench 8.6 High2022-05-17
CVE-2022-0573 JFrog Artifactory 代码问题漏洞 — JFrog Artifactory 8.8 High2022-05-16
CVE-2022-1463 Booking Calendar <= 9.1 - PHP Object Injection via Shortcode — Booking Calendar 8.8 High2022-05-10
CVE-2021-21956 CloudLinux Imunify360 代码问题漏洞 — Imunify360 8.4 -2022-04-14
CVE-2022-23450 Siemens SIMATIC 代码问题漏洞 — SIMATIC Energy Manager Basic 9.8 -2022-04-12
CVE-2022-20763 Cisco Webex Meetings Java Deserialization Vulnerability — Cisco Webex Meetings 5.4 Medium2022-04-06
CVE-2022-1032 Insecure deserialization of not validated module file in crater-invoice/crater — crater-invoice/crater 7.2 -2022-03-29
CVE-2019-6834 Schneider Electric Software Update 代码问题漏洞 — Software Update (SESU) – SUT Service component 7.3 High2022-03-28
CVE-2021-27475 Rockwell Automation Connected Components Workbench Deserialization of Untrusted Data — Connected Components Workbench 8.6 High2022-03-23
CVE-2021-27470 Rockwell Automation FactoryTalk AssetCentre Deserialization of Untrusted Data — FactoryTalk AssetCentre 10.0 Critical2022-03-23
CVE-2021-27466 Rockwell Automation FactoryTalk AssetCentre Deserialization of Untrusted Data — FactoryTalk AssetCentre 10.0 Critical2022-03-23
CVE-2021-27462 Rockwell Automation FactoryTalk AssetCentre Deserialization of Untrusted Data — FactoryTalk AssetCentre 10.0 Critical2022-03-23
CVE-2021-27460 Rockwell Automation FactoryTalk AssetCentre Deserialization of Untrusted Data — FactoryTalk AssetCentre 10.0 Critical2022-03-23
CVE-2022-24282 Siemens SINEC NMS 代码问题漏洞 — SINEC NMS 7.2 High2022-03-08
CVE-2022-21828 Incapptic Connect 安全漏洞 — Ivanti Incapptic Connect 7.2 -2022-03-04
CVE-2022-0138 Airspan Networks Mimosa Deserialization of Untrusted Data — MMP 7.5 High2022-02-18

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