CWE-597: Use of Wrong Operator in String Comparison

VariantDraft

The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead.

View on MITRE
Back to CWE Lookup

Extended Description

In Java, using == or != to compare two strings for equality actually compares two objects for equality rather than their string values for equality. Chances are good that the two references will never be equal. While this weakness often only affects program correctness, if the equality is used for a security decision, the unintended comparison result could be leveraged to affect program security.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
JavaJavaScriptPHPNot Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-597 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-597, Use of Wrong Operator in String Comparison, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Address Use of Wrong Operator in String Comparison during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Static Analysis; recorded impacts include Other. Use these source-defined anchors to turn CWE-597 into implementation, review, and verification checks for the affected component.

CWE-597: Use of Wrong Operator in String ComparisonMITRE CWE

Triage CWE-597 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-597, Use of Wrong Operator in String Comparison, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-597

Apply MITRE's full root-cause mapping guidance when using CWE-597, Use of Wrong Operator in String Comparison. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-597 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-597, Use of Wrong Operator in String Comparison. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-597: Use of Wrong Operator in String Comparison?+

CWE-597: Use of Wrong Operator in String Comparison is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead. In Java, using == or != to compare two strings for equality actually compares two objects for equality rather than their string values for equality. Chances are good that the two references will never be equal. While this weakness often only affects program correctness, if the equality is used for a security decision, the unintended comparison result could be leveraged to affect program security.

What are the security consequences of Use of Wrong Operator in String Comparison?+

If exploited, CWE-597 (Use of Wrong Operator in String Comparison) it can compromise Other, leading to outcomes such as Other.

How do you prevent or mitigate Use of Wrong Operator in String Comparison?+

Recommended mitigations for CWE-597 include: Within Java, use .equals() to compare string values. Within JavaScript, use == to compare string values. Within PHP, use == to compare a numeric value to a string value. (PHP converts the string to a number.)

Which programming languages are affected by Use of Wrong Operator in String Comparison?+

CWE-597 commonly affects Java, JavaScript, PHP and Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-597 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement