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.

제출

수정 사항