Nama: Exposed Unsafe ActiveX Method

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).

Informasi Umum

Mode Pengenalan

Architecture and Design
Implementation

Platform yang Berlaku

Bahasa

Kelas: Not Language-Specific (Undetermined)

Teknologi

Kelas: Web Based (Undetermined)

Konsekuensi Umum

Cakupan	Dampak	Kemungkinan
Other	Varies by Context Catatan: If there is no integrity checking or origin validation, this method could be invoked by attackers. Since ActiveX controls can exercise far greater control over the operating system than typical Java or javascript, exposed methods can be subject to various vulnerabilities. Consequences depend on the implemented behaviors of those methods, and whether input validation is performed on the provided arguments.

Contoh yang Diamati

Referensi	Deskripsi
CVE-2007-1120	download a file to arbitrary folders.
CVE-2006-6838	control downloads and executes a url in a parameter
CVE-2007-0321	resultant buffer overflow

Mitigasi yang Memungkinkan

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.

Metode Deteksi

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.)
Efektivitas : High

Catatan Pemetaan Kerentanan

Justifikasi : 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.
Komentar : 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.

Referensi

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.

Pengajuan

Nama	Organisasi	Tanggal	Tanggal rilis	Version
CWE Content Team	MITRE	2007-05-07 +00:00	2007-05-07 +00:00	Draft 6

Modifikasi

Nama	Organisasi	Tanggal	Komentar
Eric Dalci	Cigital	2008-07-01 +00:00	updated Time_of_Introduction
CWE Content Team	MITRE	2008-09-08 +00:00	updated Relationships, Observed_Example, Other_Notes, Weakness_Ordinalities
CWE Content Team	MITRE	2008-10-14 +00:00	updated Description
CWE Content Team	MITRE	2008-11-24 +00:00	updated Relationships, Type
CWE Content Team	MITRE	2009-10-29 +00:00	updated Description, Other_Notes
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2012-05-11 +00:00	updated References, Relationships
CWE Content Team	MITRE	2012-10-30 +00:00	updated Potential_Mitigations
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships
CWE Content Team	MITRE	2017-11-08 +00:00	updated References, Relationships
CWE Content Team	MITRE	2023-04-27 +00:00	updated Detection_Factors, References, Relationships, Type
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2025-12-11 +00:00	updated Applicable_Platforms
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description

Detail CWE-618

CWE-618