CWE-618 Variante Incomplet

Exposed Unsafe ActiveX Method

This vulnerability occurs when an ActiveX control, designed for web browsers, exposes methods that bypass the browser's built-in security restrictions. These unsafe methods can perform actions…

Définition

What is CWE-618?

This vulnerability occurs when an ActiveX control, designed for web browsers, exposes methods that bypass the browser's built-in security restrictions. These unsafe methods can perform actions outside the browser's intended security boundaries, such as those defined by zones or domains.

ActiveX controls operate with high-level system permissions, granting them far more access to the operating system than standard web scripts like JavaScript. When a control exposes a method without proper safeguards, attackers can potentially invoke it from a malicious webpage. The risk level depends entirely on what the exposed method does and whether it validates any input it receives. Without checks to verify the origin or integrity of the call, these dangerous methods become an open gateway. Attackers can exploit them to perform unauthorized actions on a user's system, directly from the browser. The core issue is the combination of excessive system privileges and a lack of validation for who is calling the method or what data they are sending.

Impact réel

Real-world CVEs caused by CWE-618

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

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

1
Identifier un chemin de code qui traite des entrées non fiables sans validation.
2
Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.
3
Délivrer la charge utile via une requête normale et observer la réaction de l'application.
4
Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.

Exemple de code vulnérable

Vulnerable pseudo

MITRE n'a pas publié d'exemple de code pour ce CWE. Le motif ci-dessous est illustratif — voir Ressources pour les références canoniques.

Vulnérable pseudo

// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}

Exemple de code sécurisé

Secure pseudo

Sécurisé pseudo

// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}

What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.

Liste de contrôle de prévention

How to prevent CWE-618

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.

Signaux de détection

How to detect CWE-618

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

CWE-618

Don't catalog this weakness. Prove it's reachable.

Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.

Request AI Swarm Pentest

Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-618 ?

Quelle est la gravité de CWE-618 ?

MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.

Quels langages ou plateformes sont affectés par CWE-618 ?

MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.

Comment puis-je prévenir CWE-618 ?

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.

Comment Plexicus détecte et corrige CWE-618 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-618 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-618 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/618.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-618

CWE-749 Parent

Exposed Dangerous Method or Function

This vulnerability occurs when a software component exposes an API or interface containing a high-risk function that lacks proper access…

CWE-782 Frère

Exposed IOCTL with Insufficient Access Control

This vulnerability occurs when a system exposes an IOCTL (Input/Output Control) interface that performs sensitive operations, but fails to…

Ressources

Prêt à valider ce qui compte.

Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.

Réserver un Pentest