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

Thread Safety Violation High

Concurrently accessing shared data from multiple goroutines without synchronization leads to race conditions. When goroutines read and write the same variable concurrently, the order of operations becomes unpredictable, resulting in corrupted state. Using mutexes from sync package to lock access ensures only one goroutine can read or write the shared variable at a time. Missing synchronization allows uncontrolled concurrent access that can cause intermittent bugs, crashes, and unreliable behavior.

Detector ID

go/thread-safety-violation@v1.0

Category

Common Weakness Enumeration (CWE)

Tags

# race-condition # concurrency # top25-cwes