Exposed Unsafe ActiveX Method

Opis

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

ActiveX controls can exercise far greater control over the operating system than typical Java or javascript. Exposed methods can be subject to various vulnerabilities, depending on the implemented behaviors of those methods, and whether input validation is performed on the provided arguments. If there is no integrity checking or origin validation, this method could be invoked by attackers.

Skutki

• Other

  Other

Zapobieganie

• Implementation

  If you must expose a method, make sure to perform input validation on all arguments, and protect against all possible vulnerabilities.

• Architecture and Design

  Use code signing, although this does not protect against any weaknesses that are already in the control.

• Architecture and Design, System Configuration

  Where possible, avoid marking the control as safe for scripting.

Przykłady podatności

• 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

Słabość nadrzędna

• CWE-749 Exposed Dangerous Method or Function

Kiedy powstaje

• Architecture and Design
• Implementation

Dotyczy

Not Language-Specific, Web Based

Źródła

1. Developing Secure ActiveX Controls — Microsoft, 2005
2. The Art of Software Security Assessment — Mark Dowd, John McDonald, Justin Schuh, Chapter 12, "ActiveX Security", Page 749, Addison Wesley, 2006