CWE-618: Exposed Unsafe ActiveX Method

VariantIncomplete

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

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-618 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-618, Exposed Unsafe ActiveX Method, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Exposed Unsafe ActiveX Method during Implementation

MITRE associates mitigation with Implementation, Architecture and Design, and System Configuration; documented detection approaches include Automated Static Analysis; recorded impacts include Other. Use these source-defined anchors to turn CWE-618 into implementation, review, and verification checks for the affected component.

CWE-618: Exposed Unsafe ActiveX Method — MITRE CWE

Triage CWE-618 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-618, Exposed Unsafe ActiveX Method, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-618

Apply MITRE's full root-cause mapping guidance when using CWE-618, Exposed Unsafe ActiveX Method. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-618 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-618, Exposed Unsafe ActiveX Method. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-618: Exposed Unsafe ActiveX Method?+

CWE-618: Exposed Unsafe ActiveX Method is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Exposed Unsafe ActiveX Method?+

If exploited, CWE-618 (Exposed Unsafe ActiveX Method) it can compromise Other, leading to outcomes such as Other.

How do you prevent or mitigate Exposed Unsafe ActiveX Method?+

Recommended mitigations for CWE-618 include: 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.

Which programming languages are affected by Exposed Unsafe ActiveX Method?+

CWE-618 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Exposed Unsafe ActiveX Method?+

MITRE documents real CVEs mapped to CWE-618, including CVE-2007-1120, CVE-2006-6838 and CVE-2007-0321. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-618 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-618

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement