CWE-749: Exposed Dangerous Method or Function
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
常见后果
影响范围: Integrity Confidentiality Availability Access Control Other
技术影响: Gain Privileges or Assume Identity Read Application Data Modify Application Data Execute Unauthorized Code or Commands Other
说明: Exposing critical functionality essentially provides an attacker with the privilege level of the exposed functionality. This could result in the modification or exposure of sensitive data or possibly even execution of arbitrary code.
潜在缓解措施
阶段: Architecture and Design
描述: If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
阶段: Architecture and Design Implementation
策略: Attack Surface Reduction
检测方法
方法: 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-2007-6382
arbitrary Java code execution via exposed method
参考: CVE-2007-1112
security tool ActiveX control allows download or upload of files
引入模式
| 阶段 | 说明 |
|---|---|
| Architecture and Design | - |
| Implementation | - |