|
|
Status: Incomplete Weakness ID: 618 (Weakness Variant)Description Summary 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). If there is no integrity checking or origin validation, this method could be invoked by attackers. Weakness Ordinalities Primary (where the weakness exists independent of other weaknesses) Potential Mitigations If you must expose a method, make sure to perform input validation on all arguments, and protect against all possible vulnerabilities. Use code signing, although this does not protect against any weaknesses that are already in the control. Where possible, avoid marking the control as safe for scripting. Observed Examples
Other Notes 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. Alternate keywords: OLE Object, Component Object Model (COM) References Relationships
Time of Introduction  Architecture and Design ImplementationContent History Modifications Eric Dalci. Cigital. 2008-07-01. (External) updated Time_of_Introduction CWE Content Team. MITRE. 2008-09-08. (Internal) updated Relationships, Observed_Example, Other_Notes, Weakness_Ordinalities |
|
|
|||
