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

Not Recommended API Usage High

Using deprecated Amazon Web Services (AWS) APIs and outdated client initialization in Go code can introduce security risks and quality issues. Initializing old S3 or Kinesis clients without proper configuration may leak credentials or have other security flaws. Calling unsupported APIs like GetRecords and ListObjects can lead to unexpected breaks when AWS fully retires those APIs. To improve quality and security, use the latest AWS SDK client initialization patterns and avoid APIs not currently recommended per the AWS documentation. This reduces technical debt and avoids known issues with outdated clients and APIs.

Detector ID

go/not-recommended-apis@v1.0

Category

Common Weakness Enumeration (CWE)

-

Tags

# security-context