Amazon QDetector Library Sign in to Amazon Q

Q

Detector Library

Go detectors (45/45)

Useless if Body Channel Guarded With Mutex Improper Certificate Validation Unvalidated S3 Bucket Ownership Resource Leak Insecure Cookie Weak Random Number Generation Redundant Equality Check Insecure Ignore Host Key Unsafe Reflection Unchecked Batch Operation Failures Lambda Client Reuse Os Command Injection Useless if Conditional Log Injection Httptrace FileServer As Handler Pprof Endpoint Cross Site Scripting (XSS)Not Recommended API Usage Hidden Goroutine Channel Accessible By Non Endpoint Decompression Bomb Cross-Site Request Forgery (CSRF)Thread Safety Violation Insecure Connection SQL Injection Deprecated Key Generator Exported Loop Pointer Server Side Request Forgery (SSRF)Sensitive Information Leak Integer Overflow Missing Pagination Insecure Cryptography Protection Mechanism Failure Nil Pointer Dereference Temporary Files XML External Entity Insecure File Permissions Authentication Bypass By Alternate Name Code Injection Improper authentication Use Filepath Join Path Traversal Write Pprof Profile Output Hardcoded true or false

Authentication Bypass By Alternate Name High

Assigning the same variable from different untrusted sources like request parameters, session data, etc. in Go code can cause confused logic and vulnerabilities. The variable may end up with an unintended blended value from overlapping disjoint sources. To avoid inconsistent state and logic issues, variables should be assigned from a single trusted authoritative source. Consolidating assignment to one clear source of truth ensures code operates on the intended value, avoiding blended state from multiple unvalidated sources.

Detector ID

go/authentication-bypass-by-alternate-name@v1.0

Category

Common Weakness Enumeration (CWE)

Tags

-