CWE-482 Variante Borrador Low likelihood

Comparing instead of Assigning

This vulnerability occurs when a developer accidentally uses a comparison operator (like '==') where an assignment operator (like '=') was intended, creating a logic error instead of setting a value.

Definición

What is CWE-482?

This vulnerability occurs when a developer accidentally uses a comparison operator (like '==') where an assignment operator (like '=') was intended, creating a logic error instead of setting a value.
This common coding mistake happens because assignment and comparison operators look very similar in many programming languages. For example, using `if (x = 5)` instead of `if (x == 5)` assigns the value 5 to `x` and then evaluates the assignment's result as the condition, which is often always true, breaking the intended program logic. To prevent this, developers should adopt defensive coding habits like placing constants on the left side in comparisons (e.g., `if (5 == x)`), which would cause a compilation error if written incorrectly as `if (5 = x)`. Modern compilers and linters often flag this pattern with warnings like "possible unintended assignment," which should always be investigated and corrected.
Impacto en el mundo real

Real-world CVEs caused by CWE-482

Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    The following example demonstrates the weakness.

  2. 2

    The following C/C++ example shows a simple implementation of a stack that includes methods for adding and removing integer values from the stack. The example uses pointers to add and remove integer values to the stack array variable.

  3. 3

    The push method includes an expression to assign the integer value to the location in the stack pointed to by the pointer variable.

  4. 4

    However, this expression uses the comparison operator "==" rather than the assignment operator "=". The result of using the comparison operator instead of the assignment operator causes erroneous values to be entered into the stack and can cause unexpected results.

Ejemplo de código vulnerable

Vulnerable Java

The following example demonstrates the weakness.

Vulnerable Java 
void called(int foo) {
  	foo==1;
  	if (foo==1) System.out.println("foo\n");
  }
  int main() {
  		called(2);
  		return 0;
  }
Ejemplo 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 prevención

How to prevent CWE-482

  • Testing Many IDEs and static analysis products will detect this problem.
Señales de detección

How to detect CWE-482

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-482 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.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-482?

This vulnerability occurs when a developer accidentally uses a comparison operator (like '==') where an assignment operator (like '=') was intended, creating a logic error instead of setting a value.

¿Qué gravedad tiene CWE-482?

MITRE califica la probabilidad de explotación como Baja — la explotación es poco frecuente, pero la debilidad debe corregirse cuando se descubra.

¿Qué lenguajes o plataformas se ven afectados por CWE-482?

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

¿Cómo puedo prevenir CWE-482?

Many IDEs and static analysis products will detect this problem.

¿Cómo detecta y corrige Plexicus CWE-482?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-482 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-482?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/482.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-482

CWE-480 Padre

Use of Incorrect Operator

This vulnerability occurs when a developer mistakenly uses the wrong operator in their code, leading to unintended and potentially…

CWE-481 Hermano

Assigning instead of Comparing

This flaw occurs when a developer accidentally uses the assignment operator (=) instead of the comparison operator (== or ===). The code…

CWE-597 Hermano

Use of Wrong Operator in String Comparison

This vulnerability occurs when a developer incorrectly compares string values, typically by using reference equality operators (like == or…

Recursos

Further reading

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.

Comenzar gratis Reservar una demo