AWS logo
Amazon QDetector Library

High

Showing all detectors for the JavaScript language with high severity.

OS command injection

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

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.

Protection mechanism failure

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

Non-literal regular expression

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

Tainted input for Docker API

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

Usage of an API that is not recommended

APIs that are not recommended were found.

XML external entity

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

Server-side request forgery

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

Timing attack

Insecure string comparison can lead to a timing-attack.

NoSQL injection

User input can be vulnerable to injection attacks.

Insecure cookie

Insecure cookies can lead to unencrypted transmission of sensitive data.

Cross-site scripting

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

AWS credentials logged

Logging unencrypted AWS credentials can expose them to an attacker.

XPath injection

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

Path traversal

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

DNS prefetching

DNS prefetching can cause latency and privacy issues.

Insecure connection using unencrypted protocol

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

Cross-site request forgery

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

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.

Client-side KMS reencryption

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

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.

Batch request with unchecked failures

Unchecked failures can lead to data loss.

Cryptographic key generator

Insufficient key sizes can lead to brute force attacks.

Unverified hostname

Unverified hostnames lead to security vulnerabilities.

Origins-verified cross-origin communications

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

Loose file permissions

Weak file permissions can lead to privilege escalation.

Improper certificate validation

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

Deserialization of untrusted object

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

Sensitive information leak

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

Weak obfuscation of web requests

Weak obfuscation of web requests makes your application vulnerable.

Logging of sensitive information

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

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.

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.

Improper restriction of rendered UI layers or frames

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

Disabled HTML autoescape

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

Unvalidated expansion of archive files

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

File injection

Writing unsanitized user data to a file is unsafe.

Sendfile injection

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

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.

Header injection

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

Inefficient polling of AWS resource

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