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

Missing Pagination Medium

Calling AWS API methods that return paginated results without properly handling pagination can lead to incomplete data. The full result set may span multiple pages, but only the first page is returned without pagination. Failing to retrieve all pages can cause data loss or inaccurate results. Pagination should be used to automatically handle page tokens and iterate through all response pages.

Detector ID

go/missing-pagination@v1.0

Category

Common Weakness Enumeration (CWE)

Tags

# aws-go-sdk # data-integrity # security-context