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…

Definição

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 no mundo real

Real-world CVEs caused by CWE-1116

Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.

Como os atacantes a exploram

Trajeto do atacante passo a passo

  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.

Exemplo de código vulnerável

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.

Vulnerável 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; 
   } 
 }
Exemplo 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 verificação de prevenção

How to prevent CWE-1116

  • Implementation Verify that each comment accurately reflects what is intended to happen during execution of the code.
Sinais de deteção

How to detect CWE-1116

SAST High

Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.

DAST Moderate

Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.

Runtime Moderate

Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.

Code review Moderate

Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-1116 e abre um PR de correção em menos de 60 segundos.

O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o 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.

Qual a gravidade do CWE-1116?

A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.

Que linguagens ou plataformas são afetadas pelo CWE-1116?

A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.

Como posso prevenir o CWE-1116?

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

Como é que o Plexicus deteta e corrige o CWE-1116?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1116 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.

Onde posso saber mais sobre o CWE-1116?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/1116.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-1116

CWE-1078 Pai

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

Inappropriate Whitespace Style

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

CWE-1115 Irmão

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

Pronto quando você estiver

Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.

O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.

Começar grátis Reservar uma demo