Unsafe ActiveX Control Marked Safe For Scripting

Draft Variant
Structure: Simple
Description

This vulnerability occurs when an ActiveX control designed for limited use is incorrectly flagged as safe for scripting, allowing web pages to access its potentially dangerous functions.

Extended Description

ActiveX controls are reusable software components, but some contain functionality that should only run in trusted environments. When developers or packagers mistakenly mark a restricted control as 'safe for scripting,' they remove the browser's security barrier that normally blocks untrusted web pages from interacting with it. This misconfiguration lets attackers embed malicious scripts in web pages that call the control's dangerous methods. Depending on what the control can do, this could lead to data theft, system takeover, or other exploits—effectively turning a legitimate component into an attack vector through a simple marking error.

Common Consequences 1
Scope: ConfidentialityIntegrityAvailability

Impact: Execute Unauthorized Code or Commands

Potential Mitigations 2
Phase: Architecture and Design
During development, do not mark it as safe for scripting.
Phase: System Configuration
After distribution, you can set the kill bit for the control so that it is not accessible from Internet Explorer.
Observed Examples 3
CVE-2007-0617control allows attackers to add malicious email addresses to bypass spam limits
CVE-2007-0219web browser uses certain COM objects as ActiveX
CVE-2006-6510kiosk allows bypass to read files
References 4
Developing Secure ActiveX Controls
Microsoft
13-04-2005
ID: REF-503
How to stop an ActiveX control from running in Internet Explorer
Microsoft
ID: REF-510
Writing Secure Code
Michael Howard and David LeBlanc
Microsoft Press
04-12-2002
ID: REF-7
The Art of Software Security Assessment
Mark Dowd, John McDonald, and Justin Schuh
Addison Wesley
2006
ID: REF-62
Modes of Introduction
Architecture and Design
Implementation