CWE-1116 Base Incompleto

Inaccurate Comments

This weakness occurs when code comments do not correctly describe or explain the actual behavior of the associated code. Misleading comments create a disconnect between what the documentation says…

Definición

What is CWE-1116?

This weakness occurs when code comments do not correctly describe or explain the actual behavior of the associated code. Misleading comments create a disconnect between what the documentation says and what the program actually does.
Inaccurate comments introduce confusion and inefficiency during code reviews and security audits. Reviewers must spend extra time verifying actual behavior against stated intent, slowing down the validation process and increasing the risk that subtle logic errors or security flaws will be overlooked. Over time, this inconsistency makes code maintenance significantly harder, indirectly harming security. It becomes more difficult to identify root causes of bugs or vulnerabilities, and developers are more likely to introduce new defects when modifying code they do not fully understand due to misleading documentation.
Impacto en el mundo real

Real-world CVEs caused by CWE-1116

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

    In the following Java example the code performs a calculation to determine how much medicine to administer. A comment is provided to give insight into what the calculation shoud be doing. Unfortunately the comment does not match the actual code and thus leaves the reader to wonder which is correct.

  2. 2

    In the correction below, the code functionality has been verified, and the comment has been corrected to reflect the proper calculation.

  3. 3

    Note that in real-world code, these values should be validated to disallow negative numbers, prevent integer overflow, etc.

Ejemplo de código vulnerable

Vulnerable Java

In the following Java example the code performs a calculation to determine how much medicine to administer. A comment is provided to give insight into what the calculation shoud be doing. Unfortunately the comment does not match the actual code and thus leaves the reader to wonder which is correct.

Vulnerable Java 
public class Main {

```
   public static void main(String[] args) { 
  	 int pt_weight = 83;
  	 int mg_per_kg = 3;
  	 int daily_dose = 0;
  	 // Add the patient weight and Mg/Kg to calculate the correct daily dose
  	 daily_dose = pt_weight * mg_per_kg;
  	 return dosage; 
   } 
 }
Ejemplo de código seguro

Secure Java

In the correction below, the code functionality has been verified, and the comment has been corrected to reflect the proper calculation.

Seguro Java 
public class Main {

```
   public static void main(String[] args) { 
  	 int pt_weight = 83;
  	 int mg_per_kg = 3;
  	 int daily_dose = 0;
  	 // Multiply the patient weight and Mg/Kg to calculate the correct daily dose
  	 daily_dose = pt_weight * mg_per_kg;
  	 return dosage; 
   } 
 }
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-1116

  • Implementation Verify that each comment accurately reflects what is intended to happen during execution of the code.
Señales de detección

How to detect CWE-1116

SAST High

Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.

DAST Moderate

Ejecuta pruebas dinámicas de seguridad de aplicaciones (DAST) contra el endpoint en vivo.

Runtime Moderate

Vigila los logs en tiempo de ejecución para detectar trazas de excepción inusuales, entradas malformadas o intentos de bypass de autorización.

Code review Moderate

Revisión de código: marca cualquier código nuevo que maneje entrada desde esta superficie sin usar los helpers validados del framework.

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-1116 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-1116?

This weakness occurs when code comments do not correctly describe or explain the actual behavior of the associated code. Misleading comments create a disconnect between what the documentation says and what the program actually does.

¿Qué gravedad tiene CWE-1116?

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

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

Verify that each comment accurately reflects what is intended to happen during execution of the code.

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

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

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

Debilidades relacionadas

Weaknesses related to CWE-1116

CWE-1078 Padre

Inappropriate Source Code Style or Formatting

This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making…

CWE-1085 Hermano

Invokable Control Element with Excessive Volume of Commented-out Code

This weakness occurs when a callable function, method, or procedure contains a large amount of inactive, commented-out code within its…

CWE-1099 Hermano

Inconsistent Naming Conventions for Identifiers

This weakness occurs when a codebase uses mixed naming styles for elements like variables, functions, data types, or files, creating an…

CWE-1106 Hermano

Insufficient Use of Symbolic Constants

This weakness occurs when developers embed raw numbers or text strings directly in code instead of using named symbolic constants, making…

CWE-1107 Hermano

Insufficient Isolation of Symbolic Constant Definitions

This weakness occurs when a codebase uses symbolic constants (like named values for numbers or strings) but scatters their definitions…

CWE-1109 Hermano

Use of Same Variable for Multiple Purposes

This weakness occurs when a single variable is reused to handle multiple, unrelated tasks or to store different pieces of data throughout…

CWE-1113 Hermano

Inappropriate Comment Style

This weakness occurs when source code comments are written in a style or format that doesn't match the project's established standards or…

CWE-1114 Hermano

Inappropriate Whitespace Style

This weakness occurs when source code uses inconsistent or non-standard whitespace formatting, such as irregular indentation, spacing, or…

CWE-1115 Hermano

Source Code Element without Standard Prologue

This weakness occurs when source code files or modules lack a consistent, standardized header or prologue that the development team has…

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