CWE-223 Base Rascunho

Omission of Security-relevant Information

This vulnerability occurs when an application fails to capture or present crucial security-related details, such as the origin of a request or the specifics of a security event. Without this…

Definição

What is CWE-223?

This vulnerability occurs when an application fails to capture or present crucial security-related details, such as the origin of a request or the specifics of a security event. Without this information, developers and security teams cannot effectively trace attacks or validate whether an operation is legitimate.

When security-relevant information is omitted, it creates a blind spot in your application's defense. Attackers can exploit this gap to launch attacks without leaving an audit trail, making it nearly impossible to perform forensic analysis, understand the attack vector, or attribute malicious activity. This lack of visibility undermines incident response and allows threats to persist undetected. To prevent this, ensure your application logs and displays key security events with sufficient context. This includes timestamps, source IP addresses, user identifiers, affected resources, and the nature of the action performed. Implementing structured logging and real-time monitoring dashboards turns this data into actionable intelligence, helping your team quickly identify, investigate, and mitigate security incidents.

Impacto no mundo real

Real-world CVEs caused by CWE-223

CVE-1999-1029

Login attempts are not recorded if the user disconnects before the maximum number of tries.
CVE-2002-1839

Sender's IP address not recorded in outgoing e-mail.
CVE-2000-0542

Failed authentication attempts are not recorded if later attempt succeeds.

Como os atacantes a exploram

Trajeto do atacante passo a passo

1
This code logs suspicious multiple login attempts.
2
This code only logs failed login attempts when a certain limit is reached. If an attacker knows this limit, they can stop their attack from being discovered by avoiding the limit.
3
This code prints the contents of a file if a user has permission.
4
While the code logs a bad access attempt, it logs the user supplied name for the file, not the canonicalized file name. An attacker can obscure their target by giving the script the name of a link to the file they are attempting to access. Also note this code contains a race condition between the is_link() and readlink() functions (CWE-363).

Exemplo de código vulnerável

Vulnerable PHP

This code logs suspicious multiple login attempts.

Vulnerável PHP

function login($userName,$password){
  		if(authenticate($userName,$password)){
  			return True;
  		}
  		else{
  			incrementLoginAttempts($userName);
  			if(recentLoginAttempts($userName) > 5){
  				writeLog("Failed login attempt by User: " . $userName . " at " + date('r') );
  			}
  		}
  }

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

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

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

Qual a gravidade do CWE-223?

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

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

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

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

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

Fraquezas relacionadas

Weaknesses related to CWE-223

CWE-221 Pai

Information Loss or Omission

This weakness occurs when an application fails to log critical security events or records them inaccurately, which can misguide security…

CWE-222 Irmão

Truncation of Security-relevant Information

This vulnerability occurs when a system shortens or cuts off security-critical data during display, logging, or processing. This…

CWE-224 Irmão

Obscured Security-relevant Information by Alternate Name

This vulnerability occurs when a system logs or reports security-critical events using a nickname or alias for a component, instead of its…

CWE-356 Irmão

Product UI does not Warn User of Unsafe Actions

This vulnerability occurs when a software interface fails to alert users before they perform a risky action. Without clear warnings, users…

CWE-396 Irmão

Declaration of Catch for Generic Exception

This weakness occurs when code catches a generic exception type like 'Exception' or 'Throwable', which can hide specific errors and create…

CWE-397 Irmão

Declaration of Throws for Generic Exception

This vulnerability occurs when a method is declared to throw an overly broad exception type, such as a generic 'Exception' or 'Throwable'.…

CWE-451 Irmão

User Interface (UI) Misrepresentation of Critical Information

This vulnerability occurs when a user interface fails to accurately display or highlight crucial information, potentially misleading users…

CWE-1429 Filho

Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface

This vulnerability occurs when a hardware interface discards operations without providing any security-relevant feedback, such as error…

CWE-778 Filho

Insufficient Logging

This weakness occurs when an application fails to properly record important security events or captures them with insufficient detail,…

Recursos

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