Unsafe ActiveX Control Marked Safe For Scripting |
Weakness ID: 623 (Weakness Variant) | Status: Draft |
Description Summary
An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.
Extended Description
This might allow attackers to use dangerous functionality via a web page that accesses the control, which can lead to different resultant vulnerabilities, depending on the control's behavior.
Reference | Description |
---|---|
CVE-2007-0617 | add emails to spam whitelist |
CVE-2007-0219 | web browser uses certain COM objects as ActiveX |
CVE-2006-6510 | kiosk allows bypass to read files |
During development, do not mark it as safe for scripting. |
After distribution, you can set the kill bit for the control so that it is not accessible from Internet Explorer. |
Ordinality | Description |
---|---|
Primary | (where the weakness exists independent of other weaknesses) |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 267 | Privilege Defined With Unsafe Actions | Development Concepts (primary)699 Research Concepts (primary)1000 |
ChildOf | ![]() | 691 | Insufficient Control Flow Management | Research Concepts1000 |
PeerOf | ![]() | 618 | Exposed Unsafe ActiveX Method | Research Concepts1000 |
<http://msdn.microsoft.com/workshop/components/activex/safety.asp>. |
<http://msdn.microsoft.com/workshop/components/activex/security.asp>. |
<http://support.microsoft.com/kb/240797>. |
[REF-11] M. Howard and D. LeBlanc. "Writing Secure Code". Chapter 16, "What ActiveX Components Are Safe for Initialization and Safe for Scripting?" Page 510. 2nd Edition. Microsoft. 2002. |