CWE-767 Base Incompleto

Access to Critical Private Variable via Public Method

This vulnerability occurs when a class exposes a public method that directly accesses or alters a private variable.

Definição

What is CWE-767?

This vulnerability occurs when a class exposes a public method that directly accesses or alters a private variable.

Exposing a private variable through a public method breaks a core principle of encapsulation. It allows external code, including potential attacker-controlled inputs, to bypass intended controls and directly manipulate sensitive internal data. This can lead to the variable holding values the rest of the codebase never expects, corrupting the application's state and violating critical security assumptions. Beyond unexpected modification, this flaw can also lead to information disclosure. An attacker might use the public method to read the private variable's contents, potentially leaking sensitive data like internal flags, cryptographic keys, or user information. This exposed data not only compromises confidentiality but can also provide attackers with the insights needed to craft more sophisticated and targeted follow-up attacks.

Impacto no mundo real

Real-world CVEs caused by CWE-767

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
The following example declares a critical variable to be private, and then allows the variable to be modified by public methods.
2
The following example could be used to implement a user forum where a single user (UID) can switch between multiple profiles (PID).
3
The programmer implemented setPID with the intention of modifying the PID variable, but due to a typo. accidentally specified the critical variable UID instead. If the program allows profile IDs to be between 1 and 10, but a UID of 1 means the user is treated as an admin, then a user could gain administrative privileges as a result of this typo.

Exemplo de código vulnerável

Vulnerable C++

The following example declares a critical variable to be private, and then allows the variable to be modified by public methods.

Vulnerável C++

private: float price;
  public: void changePrice(float newPrice) {
  	price = newPrice;
  }

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-767

Implementation Use class accessor and mutator methods appropriately. Perform validation when accepting data from a public method that is intended to modify a critical private variable. Also be sure that appropriate access controls are being applied when a public method interfaces with critical data.

Sinais de deteção

How to detect CWE-767

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.

CWE-767

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

This vulnerability occurs when a class exposes a public method that directly accesses or alters a private variable.

Qual a gravidade do CWE-767?

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

MITRE lists the following affected platforms: C++, C#, Java.

Como posso prevenir o CWE-767?

Use class accessor and mutator methods appropriately. Perform validation when accepting data from a public method that is intended to modify a critical private variable. Also be sure that appropriate access controls are being applied when a public method interfaces with critical data.

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

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

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

Fraquezas relacionadas

Weaknesses related to CWE-767

CWE-668 Pai

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

Access to Critical Private Variable via Public Method

What is CWE-767?

Real-world CVEs caused by CWE-767

Trajeto do atacante passo a passo

Vulnerable C++

Secure pseudo

How to prevent CWE-767

How to detect CWE-767

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

Frequently asked questions

Weaknesses related to CWE-767

Exposure of Resource to Wrong Sphere

Improper Isolation of Shared Resources on System-on-a-Chip (SoC)

Assumed-Immutable Data is Stored in Writable Memory

Binding to an Unrestricted IP Address

Improper Isolation of Shared Resources in Network On Chip (NoC)

Use of Externally-Controlled Format String

Exposure of Sensitive Information to an Unauthorized Actor

Passing Mutable Objects to an Untrusted Method

Returning a Mutable Object to an Untrusted Caller

Further reading

Pronto para validar o que importa.

Verifique se o AI Swarm Pentest se adequa ao seu ambiente.

Pedido recebido. Marque o próximo passo.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`