COMMON WEAKNESS ENUMERATIONIncomplete

CWE-697

Incorrect Comparison

The product compares two entities in a security-relevant context, but the comparison is incorrect.

Abstraction

Pillar

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

The product compares two entities in a security-relevant context, but the comparison is incorrect.

Extended description

This Pillar covers several possibilities: - the comparison checks one factor incorrectly; - the comparison should consider multiple factors, but it does not check at least one of those factors at all; - the comparison checks the wrong factor.

Root cause

How and when does the problem arise?

Lifecycle phase

Implementation

Risk

What does successful exploitation lead to?

Varies by Context

Affected security scopes: Other

When the comparison is incorrect, it may lead to resultant weaknesses.

Defence

How is it prevented and fixed?

  • Follow secure coding guidelines for input handling and boundary checking.
  • Enforce strict security reviews and automated static analysis (SAST) checks.

Verification

How is it detected?

Automated Static Analysis

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.)

MITRE diagram

Weakness relationships and flow

CWE-697 MITRE diagramı
CWE-697: Common Weakness Enumeration Entry CWE-697 · DayBreach Sözlük · DayBreach