CWE-618 詳細資料

An ActiveX control is intended for use in a web browser, but it exposes dangerous methods that perform actions that are outside of the browser's security model (e.g. the zone or domain).

引入方式

Architecture and Design
Implementation

適用平台

程式語言

類別： Not Language-Specific (Undetermined)

技術

類別： Web Based (Undetermined)

常見後果

觀察到的案例

潛在緩解措施

Phases : Implementation
If you must expose a method, make sure to perform input validation on all arguments, and protect against all possible vulnerabilities.
Phases : Architecture and Design
Use code signing, although this does not protect against any weaknesses that are already in the control.
Phases : Architecture and Design // System Configuration
Where possible, avoid marking the control as safe for scripting.

偵測方法

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

漏洞對應備注

理由說明 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
備註 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

參考資料

REF-503

Developing Secure ActiveX Controls
Microsoft.
https://learn.microsoft.com/en-us/previous-versions//ms533046(v=vs.85)?redirectedfrom=MSDN

REF-62

The Art of Software Security Assessment
Mark Dowd, John McDonald, Justin Schuh.

提交

修改記錄