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

Server Side Request Forgery (SSRF) High

Using untrusted user input directly in HTTP client requests like http.Get and http.NewRequest can enable server-side request forgery (SSRF). Attackers may craft malicious input that alters request destinations to access unauthorized resources. All user data must be validated against an allowlist and sanitized before usage in constructing URLs, URIs or payloads. Failing to filter dangerous values enables SSRF by allowing request destinations to be controlled. Input validation provides the primary defense by restricting inputs to known safe values. This prevents malicious users from targeting unexpected systems through client requests.

Detector ID

go/server-side-request-forgery@v1.0

Category

Common Weakness Enumeration (CWE)

Tags

# owasp-top10 # top25-cwes