This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Code Correctness: Erroneous String Compare"
From OWASP
| Line 40: | Line 40: | ||
* [[Vulnerability 1]] | * [[Vulnerability 1]] | ||
* [[Vulnerabiltiy 2]] | * [[Vulnerabiltiy 2]] | ||
| − | |||
| − | |||
| Line 48: | Line 46: | ||
* [[Control 1]] | * [[Control 1]] | ||
* [[Control 2]] | * [[Control 2]] | ||
| − | |||
| − | |||
| − | |||
==Related [[Technical Impacts]]== | ==Related [[Technical Impacts]]== | ||
Revision as of 11:49, 23 September 2008
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Last revision (mm/dd/yy): 09/23/2008
Vulnerabilities Table of Contents
Description
Strings should be compared with the equals() method, not == or !=.
This program uses == or != to compare two strings for equality, which compares two objects for equality, not their values. Chances are good that the two references will never be equal.
Risk Factors
TBD
Examples
The following branch will never be taken.
if (args[0] == STRING_CONSTANT) {
logger.info("miracle");
}
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
Note: A reference to related CWE or CAPEC article should be added when exists. Eg:
