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

Cross-Site Request Forgery (CSRF) High

Cross-site request forgery (CSRF) vulnerabilities allow attackers to perform unauthorized actions by exploiting weaknesses in request validation and loose restrictions. Failure to properly validate inputs like tokens or origins and enabling unsafe methods without route restrictions makes it possible for attackers to construct requests that users unknowingly execute while authenticated. Fixing these issues requires adding comprehensive validation of tokens, origins, and other inputs as well as tighter restrictions on routes, HTTP methods, and CORS policies. Implementing robust validation and restrictions makes it difficult for attackers to trick users into taking unintended actions through CSRF attacks.

Detector ID

go/cross-site-request-forgery@v1.0

Category

Common Weakness Enumeration (CWE)

Tags

# owasp-top10 # top25-cwes