CWE-223 Base Brouillon

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…

Définition

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.

Impact réel

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.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

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

Exemple de code vulnérable

Vulnerable PHP

This code logs suspicious multiple login attempts.

Vulnérable 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') );
  			}
  		}
  }

Exemple de code sécurisé

Secure pseudo

Sécurisé 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.

Liste de contrôle de prévention

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.

Signaux de détection

How to detect CWE-223

SAST High

Exécuter une analyse statique (SAST) sur le code source à la recherche du motif non sécurisé dans le flux de données.

DAST Moderate

Exécuter des tests de sécurité applicative dynamique (DAST) contre le point de terminaison en ligne.

Runtime Moderate

Surveiller les journaux runtime pour détecter des traces d'exception inhabituelles, des entrées malformées ou des tentatives de contournement d'autorisation.

Code review Moderate

Revue de code : signaler tout nouveau code qui traite les entrées de cette surface sans utiliser les helpers du framework validés.

CWE-223

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

Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-223 ?

Quelle est la gravité de CWE-223 ?

MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.

Quels langages ou plateformes sont affectés par CWE-223 ?

MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.

Comment puis-je prévenir 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.

Comment Plexicus détecte et corrige CWE-223 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-223 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-223 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/223.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-223

CWE-221 Parent

Prêt à valider ce qui compte.

Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.

Réserver un Pentest

Omission of Security-relevant Information

What is CWE-223?

Real-world CVEs caused by CWE-223

Parcours de l'attaquant étape par étape

Vulnerable PHP

Secure pseudo

How to prevent CWE-223

How to detect CWE-223

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

Frequently asked questions

Weaknesses related to CWE-223

Information Loss or Omission

Truncation of Security-relevant Information

Obscured Security-relevant Information by Alternate Name

Product UI does not Warn User of Unsafe Actions

Declaration of Catch for Generic Exception

Declaration of Throws for Generic Exception

User Interface (UI) Misrepresentation of Critical Information

Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface

Insufficient Logging

Further reading

Prêt à valider ce qui compte.

Vérifiez si l'AI Swarm Pentest convient à votre environnement.

Demande reçue. Réservez la prochaine étape.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`