AWS logo
Amazon QDetector Library

JSX detectors

Showing all detectors for the JSX language.

Browse by tags
Browse all detectors by tags.
Click here →
Browse by severity
Browse all detectors by severity.
Click here →
Browse by category
Browse all detectors by category.
Click here →

Browse all detectors

Protection mechanism failure

Disabled or incorrectly used protection mechanism can lead to security vulnerabilities.

Log injection

Using untrusted inputs in a log statement can enable attackers to break the log's format, forge log entries, and bypass log monitors.

Insecure connection using unencrypted protocol

Connections that use insecure protocols transmit data in cleartext, which can leak sensitive information.

Use of a deprecated method

This code uses deprecated methods, which suggests that it has not been recently reviewed or maintained.

AWS credentials logged

Logging unencrypted AWS credentials can expose them to an attacker.

Improper input validation

Improper input validation can enable attacks and lead to unwanted behavior.

Insecure cryptography

Weak, broken, or misconfigured cryptography can lead to security vulnerabilities.

Catch and swallow exception

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

File and directory information exposure

Allowing hidden files while serving files from a given root directory can cause information leakage.

Origins-verified cross-origin communications

Unverified origins of messages and identities in cross-origin communications can lead to security vulnerabilities.

SQL injection

The use of untrusted inputs in a SQL database query can enable attackers to read, modify, or delete sensitive data in the database.

Non-literal regular expression

Non-literal input to a regular expression might lead to a denial of service attack.

Typeof expression

The typeof operator should only be compared to valid values.

Batch request with unchecked failures

Unchecked failures can lead to data loss.

Pseudorandom number generators

Using pseudorandom number generators (PRNGs) is security-sensitive.

Cryptographic key generator

Insufficient key sizes can lead to brute force attacks.

Server-side request forgery

Insufficient sanitization of potentially untrusted URLs on the server side can allow server requests to unwanted destinations.

Sensitive information leak

Exposure of sensitive information can lead to an unauthorized actor having access to the information.

File injection

Writing unsanitized user data to a file is unsafe.

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.

Cross-site request forgery

Insecure configuration can lead to a cross-site request forgery (CRSF) vulnerability.

Usage of an API that is not recommended

APIs that are not recommended were found.

Tainted input for Docker API

Passing an unsanitized user argument to a function call makes your code insecure.

Cross-site scripting

Relying on potentially untrusted user inputs when constructing web application outputs can lead to cross-site scripting vulnerabilities.

Weak obfuscation of web requests

Weak obfuscation of web requests makes your application vulnerable.

Unauthenticated Amazon SNS unsubscribe requests might succeed

Failing to set the AuthenticateOnUnsubscribe flag to True when confirming an SNS subscription can lead to unauthenticated cancellations.

Set SNS Return Subscription ARN

To always return the subscription ARN, set the ReturnSubscriptionArn argument to True.

XML external entity

Objects that parse or handle XML can lead to XML external entity (XXE) attacks when they are misconfigured.

Resource leak

Allocated resources are not released properly.

Improper access control

The software does not restrict or incorrectly restrict access to a resource from an unauthorized actor.

Loose file permissions

Weak file permissions can lead to privilege escalation.

OS command injection

Constructing operating system or shell commands with unsanitized user input can lead to inadvertently running malicious code.

Client-side KMS reencryption

Client-side decryption followed by encryption is inefficient and can lead to sensitive data leaks.

Insecure CORS policy

Cross-origin resource sharing policies that are too permissive could lead to security vulnerabilities.

Inefficient polling of AWS resource

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

New function detected

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

Missing pagination

Missing pagination on a paginated call can lead to inaccurate results.

Avoid nan in comparison

Checks if nan is used is comparison.

Header injection

Constructing HTTP response headers from user-controlled data is unsafe.

Hardcoded credentials

Hardcoded credentials can be intercepted by malicious actors.

File extension validation

Checks if the extension of a file uploaded by a user is validated before the file is saved.

NoSQL injection

User input can be vulnerable to injection attacks.

Missing Amazon S3 bucket owner condition

Not setting the Amazon S3 bucket owner condition could lead to accidentally using the wrong bucket.

Disabled HTML autoescape

Disabling the HTML autoescape mechanism exposes your web applications to attacks.

Least privilege violation

The elevated privilege level should be dropped immediately after the operation is performed.

URL redirection to untrusted site

User-controlled input that specifies a link to an external site could lead to phishing attacks and allow user credentials to be stolen.

Insufficiently protected credentials

An object attribute constructed from a user-provided input should not be passed directly to a method.

Insecure hashing

Obsolete, broken, or weak hashing algorithms can lead to security vulnerabilities.

Unsanitized input is run as code

Scripts generated from unsanitized inputs can lead to malicious behavior and inadvertently running code remotely.

Check failed records when using kinesis

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

Untrusted Amazon Machine Images

Improper filtering of Amazon Machine Images (AMIs) can result in loading an untrusted image, which is a potential security vulnerability.

Session fixation

Session fixation might allow an attacker to steal authenticated session IDs.

Data loss in a batch request

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

XPath injection

Potentially unsanitized user input in XPath queries can allow an attacker to control the query in unwanted or insecure ways.

Deserialization of untrusted object

Deserialization of untrusted objects can lead to security vulnerabilities such as, inadvertently running remote code.

Invoke super appropriately

The incorrect use of super() causes problems.

Stack trace exposure

Stack traces can be hard to use for debugging.

Timing attack

Insecure string comparison can lead to a timing-attack.

LDAP injection

LDAP queries that rely on potentially untrusted inputs can allow attackers to read or modify sensitive data, run code, and perform other unwanted actions.

Insecure cookie

Insecure cookies can lead to unencrypted transmission of sensitive data.

Sensitive data stored unencrypted due to partial encryption

Encryption that is dependent on conditional logic, such as an if...then clause, might cause unencrypted sensitive data to be stored.

Unvalidated expansion of archive files

Expanding unverified archive files without controlling the size of the expanded data can lead to zip bomb attacks.

Integer overflow

An integer overflow might cause security issues when it is used for resource management or execution control.

SNS don't bind subscribe and publish

Do not bind the SNS Publish operation with the SNS Subscribe or Create Topic operation.

Unverified hostname

Unverified hostnames lead to security vulnerabilities.

Improper restriction of rendered UI layers or frames

The application incorrectly restricts frame objects or UI layers that belong to another application or domain.

AWS client not reused in a Lambda function

Recreating AWS clients in each Lambda function invocation is expensive.

Path traversal

Creating file paths from untrusted input might give a malicious actor access to sensitive files.

Override of reserved variable names in a Lambda function

Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.

Insecure temporary file or directory

Insecure ways of creating temporary files and directories can lead to race conditions, privilege escalation, and other security vulnerabilities.

Logging of sensitive information

The logging of sensitive information can expose the information to potential attackers.

Hardcoded IP address

Hardcoding an IP address can cause security problems.

Insecure object attribute modification

Updating object attributes obtained from external sources is security sensitive.

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.

DNS prefetching

DNS prefetching can cause latency and privacy issues.

Limit request length

Significant content length can lead to denial of service.

Sendfile injection

The software allows user input to control or influence paths or file names that are used in file system operations.

Improper certificate validation

Lack of validation of a security certificate can lead to host impersonation and sensitive data leaks.