The product compares two entities in a security-relevant context, but the comparison is incorrect.
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.
When the comparison is incorrect, it may lead to resultant weaknesses.
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.)