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

Unchecked Batch Operation Failures Info

Calling AWS batch APIs in Go without checking for errors can lead to silent failures and data loss. Batch operations like SNS PublishBatch can partially succeed but still contain failed items. To prevent data loss, always check the error response of batch calls. Handle any failed items or errors returned. Checking the batch API result ensures critical failures are not missed. This avoids losing data due to unhandled batch operation failures.

Detector ID

go/aws-unchecked-batch-failures@v1.0

Category

Common Weakness Enumeration (CWE)

Tags

# batch-operations # data-integrity