Amazon QDetector Library Sign in to Amazon Q

Amazon Q

Detector Library

JavaScript detectors (95/95)

Improper access control Sensitive data stored unencrypted due to partial encryption Pseudorandom number generators OS command injection URL redirection to untrusted site Improper Output Handling Integer overflow Protection mechanism failure Non-literal regular expression Tainted input for Docker API Usage of an API that is not recommended XML external entity Server-side request forgery New function detected Stack trace exposure Timing attack SNS don't bind subscribe and publish Invoke super appropriately NoSQL injection Improper handling of case sensitivity Hardcoded credentials Lazy Load Module Insecure cookie Cross-site scripting Use {} instead of new Object()Hardcoded IP address AWS credentials logged Sensitive query string XPath injection Data loss in a batch request Path traversal Least privilege violation DNS prefetching Resource leak Insufficiently protected credentials File extension validation Insecure connection using unencrypted protocol Cross-site request forgery Set SNS Return Subscription ARN File and directory information exposure Missing Amazon S3 bucket owner condition Insecure hashing Numeric truncation error Client-side KMS reencryption Clear text credentials AWS client not reused in a Lambda function LDAP injection Batch request with unchecked failures Items removed from an array using delete Cryptographic key generator Unauthenticated Amazon SNS unsubscribe requests might succeed Improper Synchronization Unverified hostname Avoid Undefined As Variable Name Origins-verified cross-origin communications Loose file permissions Unsanitized input is run as code Alert Box JS Rule Untrusted Amazon Machine Images File Race Bad Improper certificate validation Insecure CORS policy Redundant switch statement Unbounded LLM Output Deserialization of untrusted object Sensitive information leak Index of method comparison Check failed records when using kinesis Weak obfuscation of web requests Catch and swallow exception Logging of sensitive information Limit request length String passed to `setInterval` or `setTimeout`Improper Initialization Untrusted data in security decision Missing check on method output Log injection Override of reserved variable names in a Lambda function Improper restriction of rendered UI layers or frames Insecure cryptography Insecure object attribute modification Session fixation Type confusion Avoid nan in comparison Improper input validation Disabled HTML autoescape Use of a deprecated method Unvalidated expansion of archive files File injection Sendfile injection SQL injection Header injection Insecure temporary file or directory Vector embedding weaknesses Inefficient polling of AWS resource

Code Quality detectors

New function detected

Use of new Function() can be dangerous if used to evaluate dynamic content.

Invoke super appropriately

The incorrect use of super() causes problems.

Lazy Load Module

Checks for lazy module loading.

Use {} instead of new Object()

New Object() has been used for object creation instead of {}.

Numeric truncation error

Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.

Items removed from an array using delete

Items removed from an array using delete can cause undefined holes in the array.

Avoid Undefined As Variable Name

Checks if the undefined is used as variable.

Alert Box JS Rule

Checks for the use of browser pop-ups (alert, confirm, prompt).

Redundant switch statement

Detect switch statements if it has less than three case clauses.

Index of method comparison

indexOf method should not be compared with values greater than zero.

Check failed records when using kinesis

A batch request that doesn't check for failed records can lead to loss of data.

Catch and swallow exception

Swallowing exceptions, without rethrowing or logging them, can make it hard to understand why your application is failing.

String passed to `setInterval` or `setTimeout`

String passed to setInterval or setTimeout can cause the JavaScript engine to evaluate, which can lead to a security risk.

Improper Initialization

The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.

Missing check on method output

Missing checks might cause silent failures that are harder to debug.

Avoid nan in comparison

Checks if nan is used is comparison.

Inefficient polling of AWS resource

Custom polling can be inefficient and prone to error. Consider using AWS waiters instead.