Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.
CWE-223 Base Borrador
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…
Definición
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 en el mundo real
Real-world CVEs caused by CWE-223
-
Login attempts are not recorded if the user disconnects before the maximum number of tries.
-
Sender's IP address not recorded in outgoing e-mail.
-
Failed authentication attempts are not recorded if later attempt succeeds.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 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).
Ejemplo de código vulnerable
Vulnerable PHP
This code logs suspicious multiple login attempts.
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') );
}
}
} Ejemplo de código seguro
Secure 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 prevención
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.
Señales de detección
How to detect CWE-223
Ejecuta pruebas dinámicas de seguridad de aplicaciones (DAST) contra el endpoint en vivo.
Vigila los logs en tiempo de ejecución para detectar trazas de excepción inusuales, entradas malformadas o intentos de bypass de autorización.
Revisión de código: marca cualquier código nuevo que maneje entrada desde esta superficie sin usar los helpers validados del framework.
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.
Preguntas frecuentes ¿Qué es CWE-223?
¿Qué gravedad tiene CWE-223?
¿Qué lenguajes o plataformas se ven afectados por CWE-223?
¿Cómo puedo prevenir CWE-223?
¿Cómo detecta y corrige Plexicus CWE-223?
¿Dónde puedo aprender más sobre CWE-223?
Frequently asked questions
¿Qué es 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.
¿Qué gravedad tiene CWE-223?
MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.
¿Qué lenguajes o plataformas se ven afectados por CWE-223?
MITRE no ha especificado plataformas afectadas para esta CWE — puede aplicar a la mayoría de los stacks de aplicaciones.
¿Cómo puedo prevenir 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.
¿Cómo detecta y corrige Plexicus CWE-223?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-223 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-223?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/223.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-223
CWE-221 Padre
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 Hermano
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 Hermano
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 Hermano
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 Hermano
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 Hermano
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 Hermano
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 Hijo
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 Hijo
Insufficient Logging
This weakness occurs when an application fails to properly record important security events or captures them with insufficient detail,…
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.