CWE-1108 Base Incompleto

Excessive Reliance on Global Variables

This weakness occurs when a codebase depends too heavily on global variables to store and manage state, rather than keeping data within appropriate local scopes like functions or classes.

Definição

What is CWE-1108?

This weakness occurs when a codebase depends too heavily on global variables to store and manage state, rather than keeping data within appropriate local scopes like functions or classes.
Excessive use of global variables creates a tightly coupled and fragile architecture. It becomes difficult to track where and how data is modified, leading to unpredictable side effects across the entire application. This lack of encapsulation makes the code harder to understand, test, and debug, as changes in one module can silently break functionality in another. From a security perspective, this poor maintainability indirectly increases risk. It slows down the identification and remediation of actual vulnerabilities because developers must navigate a complex web of dependencies. Furthermore, the constant risk of unintended interactions makes it easier to introduce new security flaws during routine maintenance or feature development.
Impacto no mundo real

Real-world CVEs caused by CWE-1108

Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.

Como os atacantes a exploram

Trajeto do atacante passo a passo

  1. 1

    Identificar um caminho de código que trata input não confiável sem validação.

  2. 2

    Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.

  3. 3

    Entregar o payload através de um pedido normal e observar a reação da aplicação.

  4. 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-1108

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Sinais de deteção

How to detect CWE-1108

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

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-1108 e abre um PR de correção em menos de 60 segundos.

O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o CWE-1108?

This weakness occurs when a codebase depends too heavily on global variables to store and manage state, rather than keeping data within appropriate local scopes like functions or classes.

Qual a gravidade do CWE-1108?

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-1108?

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-1108?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

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

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1108 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-1108?

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

Fraquezas relacionadas

Weaknesses related to CWE-1108

CWE-1076 Pai

Insufficient Adherence to Expected Conventions

This weakness occurs when software code, design, documentation, or other components fail to follow established industry or…

CWE-1045 Irmão

Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor

This occurs when a base class defines a virtual destructor, but a derived class inherits from it without declaring its own virtual…

CWE-1070 Irmão

Serializable Data Element Containing non-Serializable Item Elements

This weakness occurs when a class or data structure is marked as serializable, but it contains one or more member elements that cannot be…

CWE-1078 Irmão

Inappropriate Source Code Style or Formatting

This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making…

CWE-1079 Irmão

Parent Class without Virtual Destructor Method

This occurs when a base class, designed to be inherited from, does not declare its destructor as virtual. This oversight prevents proper…

CWE-1082 Irmão

Class Instance Self Destruction Control Element

This vulnerability occurs when an object's code contains logic that triggers its own deletion or destruction during runtime.

CWE-1087 Irmão

Class with Virtual Method without a Virtual Destructor

This occurs when a class defines a virtual method but does not also provide a virtual destructor.

CWE-1091 Irmão

Use of Object without Invoking Destructor Method

This weakness occurs when a program accesses an object but fails to properly call its destructor or finalizer method. This leaves the…

CWE-1097 Irmão

Persistent Storable Data Element without Associated Comparison Control Element

This weakness occurs when a persistent data object lacks the necessary methods to be properly compared, which can lead to inconsistent or…

Recursos

Further reading

Pronto quando você estiver

Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.

O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.

Começar grátis Reservar uma demo