Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.
CWE-1023 Clase Incompleto
Incomplete Comparison with Missing Factors
This weakness occurs when a program compares two items but fails to check all the necessary attributes that define their true relationship. The incomplete check can cause the software to treat…
Definición
What is CWE-1023?
This weakness occurs when a program compares two items but fails to check all the necessary attributes that define their true relationship. The incomplete check can cause the software to treat different items as identical or make incorrect security decisions.
Incomplete comparisons happen when a developer writes a check that only validates a subset of an object's or user's identity. For example, a system might authenticate a user by checking only a username without verifying the associated password or session token, or it might compare data objects using only an ID field while ignoring a critical 'type' or 'state' field. This creates a logical gap where two distinct entities can be incorrectly evaluated as equivalent.
This flaw directly undermines security and logic by allowing unauthorized access, privilege escalation, or data corruption. Attackers can exploit it by providing an entity that matches on the checked factors but differs maliciously on the unchecked ones. To prevent this, always ensure comparison functions validate every unique and security-relevant property that defines an entity's complete identity within that specific context.
Impacto en el mundo real
Real-world CVEs caused by CWE-1023
-
PHP remote file inclusion in web application that filters "http" and "https" URLs, but not "ftp".
-
Product does not prevent access to restricted directories due to partial string comparison with a public directory
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
Consider an application in which Truck objects are defined to be the same if they have the same make, the same model, and were manufactured in the same year.
- 2
Here, the equals() method only checks the make and model of the Truck objects, but the year of manufacture is not included.
- 3
This example defines a fixed username and password. The AuthenticateUser() function is intended to accept a username and a password from an untrusted user, and check to ensure that it matches the username and password. If the username and password match, AuthenticateUser() is intended to indicate that authentication succeeded.
- 4
In AuthenticateUser(), the strncmp() call uses the string length of an attacker-provided inPass parameter in order to determine how many characters to check in the password. So, if the attacker only provides a password of length 1, the check will only examine the first byte of the application's password before determining success.
- 5
As a result, this partial comparison leads to improper authentication (CWE-287).
Ejemplo de código vulnerable
Vulnerable Java
Consider an application in which Truck objects are defined to be the same if they have the same make, the same model, and were manufactured in the same year.
public class Truck {
private String make;
private String model;
private int year;
public boolean equals(Object o) {
if (o == null) return false;
if (o == this) return true;
if (!(o instanceof Truck)) return false;
Truck t = (Truck) o;
return (this.make.equals(t.getMake()) && this.model.equals(t.getModel()));
}
} Payload del atacante
Any of these passwords would still cause authentication to succeed for the "admin" user:
p
pa
pas
pass 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-1023
- Testing Thoroughly test the comparison scheme before deploying code into production. Perform positive testing as well as negative testing.
Señales de detección
How to detect CWE-1023
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.
Plexicus detecta automáticamente CWE-1023 y abre un PR de corrección en menos de 60 segundos.
Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.
Preguntas frecuentes ¿Qué es CWE-1023?
¿Qué gravedad tiene CWE-1023?
¿Qué lenguajes o plataformas se ven afectados por CWE-1023?
¿Cómo puedo prevenir CWE-1023?
¿Cómo detecta y corrige Plexicus CWE-1023?
¿Dónde puedo aprender más sobre CWE-1023?
Frequently asked questions
¿Qué es CWE-1023?
This weakness occurs when a program compares two items but fails to check all the necessary attributes that define their true relationship. The incomplete check can cause the software to treat different items as identical or make incorrect security decisions.
¿Qué gravedad tiene CWE-1023?
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-1023?
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-1023?
Thoroughly test the comparison scheme before deploying code into production. Perform positive testing as well as negative testing.
¿Cómo detecta y corrige Plexicus CWE-1023?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-1023 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-1023?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/1023.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-1023
CWE-697 Padre
Incorrect Comparison
This weakness occurs when a security-critical decision relies on a flawed comparison between two pieces of data. The incorrect logic can…
CWE-1024 Hermano
Comparison of Incompatible Types
This vulnerability occurs when code directly compares two values of fundamentally different data types, which can lead to unreliable or…
CWE-1025 Hermano
Comparison Using Wrong Factors
This weakness occurs when a program compares two items but checks the wrong properties or attributes. This flawed comparison leads to…
CWE-1039 Hermano
Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism
This vulnerability occurs when a system uses automated AI or machine learning to classify complex inputs like images, audio, or text, but…
CWE-1077 Hermano
Floating Point Comparison with Incorrect Operator
This vulnerability occurs when code compares two floating-point numbers using direct equality operators (like == or !=) without accounting…
CWE-1254 Hermano
Incorrect Comparison Logic Granularity
This vulnerability occurs when a system compares sensitive data, like passwords or authentication tokens, piece-by-piece instead of as a…
CWE-183 Hermano
Permissive List of Allowed Inputs
This vulnerability occurs when an application's security filter uses an allowlist that is too broad, mistakenly permitting dangerous…
CWE-185 Hermano
Incorrect Regular Expression
This vulnerability occurs when a regular expression is written incorrectly, causing it to match or validate data in unintended and…
CWE-581 Hermano
Object Model Violation: Just One of Equals and Hashcode Defined
This vulnerability occurs when a Java class defines either the equals() method or the hashCode() method, but not both, breaking a…
Listo cuando tú lo estés
Deja de pagar por desarrollador.
Empieza a cerrar el bucle.
Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.