CWE-618 Variante Incompleto

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…

Definição

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.

Impacto no mundo real

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

Como os atacantes a exploram

Trajeto do atacante passo a passo

1
Identificar um caminho de código que trata input não confiável sem validação.
2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.

Exemplo de código vulnerável

Vulnerable pseudo

A MITRE não publicou um exemplo de código para este CWE. O padrão abaixo é ilustrativo — consulte os Recursos para referências canónicas.

Vulnerável pseudo

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

Exemplo de código seguro

Secure pseudo

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

Lista de verificação de prevenção

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.

Sinais de deteção

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

Perguntas frequentes

Frequently asked questions

O que é o CWE-618?

Qual a gravidade do CWE-618?

A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.

Que linguagens ou plataformas são afetadas pelo CWE-618?

A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.

Como posso prevenir o 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.

Como é que o Plexicus deteta e corrige o CWE-618?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-618 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.

Onde posso saber mais sobre o CWE-618?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/618.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-618

CWE-749 Pai

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 Irmão

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…

Recursos

Pronto para validar o que importa.

O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.

Reservar Pentest