CWE-502: Deserialization of Untrusted Data
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
常见后果
影响范围: 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 unauthorized actions, such as generating a shell.
潜在缓解措施
阶段: 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
阶段: 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 constantly being discovered, so this alone is not a sufficient mitigation.
阶段: Architecture and Design Implementation
描述: Employ cryptography of the data or code for protection. However, it's important to note that it would still be client-side security. This is risky because if the client is compromised then the security implemented on the client (the cryptography) can be bypassed.
阶段: Operation
策略: Firewall
描述: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
有效性: Moderate
检测方法
方法: Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
有效性: High
观察示例
参考: CVE-2024-37052
insecure deserialization in platform for managing AI/ML applications and models allows code execution via a crafted pickled object in a model file
参考: CVE-2024-37288
deserialization of untrusted YAML data in dashboard for data query and visualization of Elasticsearch data
参考: CVE-2024-9314
PHP object injection in WordPress plugin for AI-based SEO
参考: CVE-2019-12799
chain: bypass of untrusted deserialization issue (CWE-502) by using an assumed-trusted class (CWE-183)
参考: CVE-2015-8103
Deserialization issue in commonly-used Java library allows remote execution.
参考: CVE-2015-4852
Deserialization issue in commonly-used Java library allows remote execution.
参考: CVE-2013-1465
Use of PHP unserialize function on untrusted input allows attacker to modify application configuration.
参考: CVE-2012-3527
Use of PHP unserialize function on untrusted input in content management system might allow code execution.
参考: CVE-2012-0911
Use of PHP unserialize function on untrusted input in content management system allows code execution using a crafted cookie value.
参考: CVE-2012-0911
Content management system written in PHP allows unserialize of arbitrary objects, possibly allowing code execution.
参考: CVE-2011-2520
Python script allows local users to execute code via pickled data.
参考: CVE-2012-4406
Unsafe deserialization using pickle in a Python script.
参考: CVE-2003-0791
Web browser allows execution of native methods via a crafted string to a JavaScript function that deserializes the string.
引入模式
| 阶段 | 说明 |
|---|---|
| Architecture and Design | OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase. |
| Implementation | - |
适用平台
编程语言
技术
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| CLASP | - | Deserialization of untrusted data | - |
| The CERT Oracle Secure Coding Standard for Java (2011) | SER01-J | Do not deviate from the proper signatures of serialization methods | - |
| The CERT Oracle Secure Coding Standard for Java (2011) | SER03-J | Do not serialize unencrypted, sensitive data | - |
| The CERT Oracle Secure Coding Standard for Java (2011) | SER06-J | Make defensive copies of private mutable components during deserialization | - |
| The CERT Oracle Secure Coding Standard for Java (2011) | SER08-J | Do not use the default serialized form for implementation defined invariants | - |
| Software Fault Patterns | SFP25 | Tainted input to variable | - |