CWE-1061 Classe Incompleto

Insufficient Encapsulation

This weakness occurs when a software component exposes too much of its internal workings, such as data structures or implementation logic. This lack of proper boundaries allows other parts of the…

Definição

What is CWE-1061?

This weakness occurs when a software component exposes too much of its internal workings, such as data structures or implementation logic. This lack of proper boundaries allows other parts of the system to interact with it in unintended ways, potentially leading to corrupted data, unexpected behavior, or hidden dependencies.
Insufficient encapsulation creates a fragile codebase where changes in one module can have unpredictable ripple effects across the system. This directly increases maintenance costs and complexity, as developers must spend extra time tracing these unintended couplings instead of focusing on core functionality or security fixes. From a security perspective, this architectural flaw indirectly introduces risk. It becomes harder to identify and patch vulnerabilities because the code's behavior is less predictable and more scattered. Furthermore, the constant need to work around these exposed internals makes it easier for developers to accidentally introduce new security bugs during routine maintenance or feature development.
Impacto no mundo real

Real-world CVEs caused by CWE-1061

  • CVE-2010-3860

    variables declared public allow remote read of system properties such as user name and home directory.

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 C++

The following example shows a basic user account class that includes member variables for the username and password as well as a public constructor for the class and a public method to authorize access to the user account.

Vulnerável C++ 
#define MAX_PASSWORD_LENGTH 15
  #define MAX_USERNAME_LENGTH 15
  class UserAccount
  {
  		public:
  				UserAccount(char *username, char *password)
  				{
  					if ((strlen(username) > MAX_USERNAME_LENGTH) ||
  					(strlen(password) > MAX_PASSWORD_LENGTH)) {
  						ExitError("Invalid username or password");
  					}
  					strcpy(this->username, username);
  					strcpy(this->password, password);
  				}
  		int authorizeAccess(char *username, char *password)
  		{
  				if ((strlen(username) > MAX_USERNAME_LENGTH) ||
  				(strlen(password) > MAX_PASSWORD_LENGTH)) {
  					ExitError("Invalid username or password");
  				}
```
// if the username and password in the input parameters are equal to* 
  				
  				
  				 *// the username and password of this account class then authorize access* 
  				if (strcmp(this->username, username) ||
  				strcmp(this->password, password))
  				```
  					return 0;
```
// otherwise do not authorize access* 
  				else
  				```
  					return 1;
  		}
  		char username[MAX_USERNAME_LENGTH+1];
  		char password[MAX_PASSWORD_LENGTH+1];
  };
Exemplo de código seguro

Secure C++

However, the member variables username and password are declared public and therefore will allow access and changes to the member variables to anyone with access to the object. These member variables should be declared private as shown below to prevent unauthorized access and changes.

Seguro C++ 
class UserAccount
  {
  public:
  	...
  private:
  	char username[MAX_USERNAME_LENGTH+1];
  	char password[MAX_PASSWORD_LENGTH+1];
  };
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-1061

  • 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-1061

SAST High

Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.

DAST Moderate

Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.

Runtime Moderate

Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.

Code review Moderate

Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-1061 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-1061?

This weakness occurs when a software component exposes too much of its internal workings, such as data structures or implementation logic. This lack of proper boundaries allows other parts of the system to interact with it in unintended ways, potentially leading to corrupted data, unexpected behavior, or hidden dependencies.

Qual a gravidade do CWE-1061?

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

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

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

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

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

Fraquezas relacionadas

Weaknesses related to CWE-1061

CWE-710 Pai

Improper Adherence to Coding Standards

This weakness occurs when developers don't consistently follow established coding standards and best practices, which can introduce…

CWE-1041 Irmão

Use of Redundant Code

This weakness occurs when a codebase contains identical or nearly identical logic duplicated across multiple functions, methods, or…

CWE-1044 Irmão

Architecture with Number of Horizontal Layers Outside of Expected Range

This occurs when a software system is built with either too many or too few distinct architectural layers, falling outside a recommended…

CWE-1048 Irmão

Invokable Control Element with Large Number of Outward Calls

This weakness occurs when a single function, method, or callable code block makes an excessively high number of calls to other objects or…

CWE-1059 Irmão

Insufficient Technical Documentation

This weakness occurs when a software or hardware product lacks comprehensive technical documentation. Missing or incomplete details about…

CWE-1065 Irmão

Runtime Resource Management Control Element in a Component Built to Run on Application Servers

This weakness occurs when an application built to run on a managed application server bypasses the server's high-level APIs and instead…

CWE-1066 Irmão

Missing Serialization Control Element

This weakness occurs when a class or data structure is marked as serializable but lacks the required control methods to properly handle…

CWE-1068 Irmão

Inconsistency Between Implementation and Documented Design

This weakness occurs when the actual code implementation deviates from the intended design described in its official documentation,…

CWE-1076 Irmão

Insufficient Adherence to Expected Conventions

This weakness occurs when software code, design, documentation, or other components fail to follow established industry 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