Exposed Unsafe ActiveX Method
Incomplete Variant
Structure: Simple
Description
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.
Common Consequences 1
Scope: Other
Impact: Other
Detection Methods 1
Automated Static AnalysisHigh
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.)Potential Mitigations 3
Phase: Implementation
If you must expose a method, make sure to perform input validation on all arguments, and protect against all possible vulnerabilities.
Phase: Architecture and Design
Use code signing, although this does not protect against any weaknesses that are already in the control.
Phase: Architecture and DesignSystem Configuration
Where possible, avoid marking the control as safe for scripting.
Observed Examples 3
CVE-2007-1120download a file to arbitrary folders.
CVE-2006-6838control downloads and executes a url in a parameter
CVE-2007-0321resultant buffer overflow
References 2
Developing Secure ActiveX Controls
Microsoft
13-04-2005
https://learn.microsoft.com/en-us/previous-versions//ms533046(v=vs.85)?redirectedfrom=MSDN(2023-04-07)
ID: REF-503
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
Related Weaknesses