Unsafe ActiveX Control Marked Safe For Scripting

Opis

An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.

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.

Skutki

• Confidentiality, Integrity, Availability

  Execute Unauthorized Code or Commands

Zapobieganie

• Architecture and Design

  During development, do not mark it as safe for scripting.

• System Configuration

  After distribution, you can set the kill bit for the control so that it is not accessible from Internet Explorer.

Przykłady podatności

• CVE-2007-0617 control allows attackers to add malicious email addresses to bypass spam limits
• CVE-2007-0219 web browser uses certain COM objects as ActiveX
• CVE-2006-6510 kiosk allows bypass to read files

Słabość nadrzędna

• CWE-267 Privilege Defined With Unsafe Actions

Pokrewna

• CWE-618 Exposed Unsafe ActiveX Method

Kiedy powstaje

• Architecture and Design
• Implementation

Dotyczy

Not Language-Specific, Web Based

Źródła

1. Developing Secure ActiveX Controls — Microsoft, 2005
2. How to stop an ActiveX control from running in Internet Explorer — Microsoft
3. Writing Secure Code — Michael Howard, David LeBlanc, Chapter 16, "What ActiveX Components Are Safe for Initialization and Safe for Scripting?" Page 510, Microsoft Press, 2002
4. The Art of Software Security Assessment — Mark Dowd, John McDonald, Justin Schuh, Chapter 12, "ActiveX Security", Page 749, Addison Wesley, 2006