Amazon Q
Detector Library
PHP detectors (34/34)
Server Side Request ForgerySQL InjectionActivated Debug FeatureSensitive information leakLog InjectionOrigins-verified cross-origin communicationsCross-site scriptingDangerous Function UsagePath TraversalAvoiding Exceptions in PHPOS command injectionIncorrect ComparisonLdap Bind Without PasswordSendfile InjectionAssert UseLoose file permissionsImproper AuthenticationInsecure connectionWeak Random Number GenerationOpen RedirectAllow Url Fopen Or IncludeInsecure cryptographyObject Input Stream Insecure DeserializationCookie Without Http Only FlagCode InjectionZip bomb attackUnsafe ReflectionSecure Signal HandlingDeserialization of untrusted dataStatic Initialization Vector (IV)Coral Csrf RuleInsecure cookieImproper access controlInsecure Object Attribute Modification
Incorrect Comparison High
Encouraging subject practices in comparing hash values or sensitive data, this recommendation underscores the use of type-safe comparison (===) over loose equality (==). Mitigating risk tied to type juggling, this enhances reliability and security in the codebase.
Detector ID
php/incorrect-comparison@v1.0
Category
Common Weakness Enumeration (CWE) 
Tags
-
Noncompliant example
1// Noncompliant: Used loose equality (`==`)
2md5("240610708") == "0";Compliant example
1// Compliant: used type-safe comparison (`===`)
2md5("240610708") === "0";