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.
Potential Impact
Other
Other
Mitigations & Prevention
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.
Detection Methods
- Automated Static Analysis High — 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 sea
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| 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 |
Related Weaknesses
Frequently Asked Questions
What is CWE-618?
CWE-618 (Exposed Unsafe ActiveX Method) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Variant-level weakness. 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).
How can CWE-618 be exploited?
Attackers can exploit CWE-618 (Exposed Unsafe ActiveX Method) to other. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.
How do I prevent CWE-618?
Key mitigations include: If you must expose a method, make sure to perform input validation on all arguments, and protect against all possible vulnerabilities.
What is the severity of CWE-618?
CWE-618 is classified as a Variant-level weakness (Low-Medium abstraction). It has been observed in 3 real-world CVEs.