CWE-103: Struts: Incomplete validate() Method Definition
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product has a validator form that either does not define a validate() method, or defines a validate() method but does not call super.validate().
扩展描述
If the code does not call super.validate(), the Validation Framework cannot check the contents of the form against a validation form. In other words, the validation framework will be disabled for the given form.
常见后果
影响范围: Other
技术影响: Other
说明: Disabling the validation framework for a form exposes the product to numerous types of attacks. Unchecked input is the root cause of vulnerabilities like cross-site scripting, process control, and SQL injection.
影响范围: Confidentiality Integrity Availability Other
技术影响: Other
说明: Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.
潜在缓解措施
阶段: Implementation
描述: Implement the validate() method and call super.validate() within that method.
检测方法
方法: 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
引入模式
| 阶段 | 说明 |
|---|---|
| Implementation | - |
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| 7 Pernicious Kingdoms | - | Struts: Erroneous validate() Method | - |
| Software Fault Patterns | SFP24 | Tainted input to command | - |